1VV0301678 Rev. 5 Page 26 of 39 01/02/2021
For simWISE, the setting shall be:
AT+CGDCONT=1, "IP","NXT17.NET"
Refer to [6] §3.6.4 for further information
2. Quickly test that connectivity is working. Issue
AT#PING="www.telit.com" and wait for response like this #PING:
01,"35.202.235.194",4,4
3. Let the LwM2M client handle the connection and the PDP context startup by issuing:
AT#SGACT=1,0
This sets the connection in inactive state.
Test LwM2M agent
1. Run the AT#LWM2MENA=1 (refer to the AT definition: AT#LWM2MENA=<en>).
2. The LwM2M client will perform the Bootstrap (only the first time or when forced)
and the terminal will receive the following URC:
LWM2M-TLT:"BOOTSTRAPPING",SSID=0,"coaps://bs.telit.io"
LWM2M-TLT:"BOOTSTRAPPED",SSID=0,"coaps://bs.telit.io"
3. After the Bootstrap, the LwM2M client will perform the registration on the DM
server, and if the service is enabled through AT#LWM2MW=0,33211,0,0,1,1
command, the following URC are received:
LWM2M-TLT:"REGISTERING",SSID=99,"coaps://api-
dev.devicewise.com"
LWM2M-TLT:"REGISTERED",SSID=99,"coaps://api-dev.devicewise.com"
At this point, as soon as the bootstrap phase has been completed, the user must check on
the IoT Portal if the registration has been completed correctly, on the IoT Portal > Things >
Overview the “Last seen” field reports:
• Lifetime expired/not expired (green/red clip)
• Elapsed time since the last Registration Update
To make sure that the connection is up, it is recommended to check that the PDP context
settings are correct. After enabling LwM2M, context should be active: this can be verified
by running AT+COPS? and AT+CGACT?
The following examples show an active PDP context is present on slot 1
AT+CGACT?
+CGACT: 1,1
+CGACT: 2,0
+CGACT: 3,0
+CGACT: 4,0
+CGACT: 5,0
+CGACT: 6,0
OK).
at+cops?
+COPS: 0,0,"vodafone IT",0
OK