Help with LTE connection after loss of connection

RE: Help with LTE connection after loss of connection

Achim Kraus — Wed, 23 Oct 2024 09:31:12 GMT

> Try:

> # DTLS update address using CID on newer records.
> # Default: true
> # DTLS.UPDATE_ADDRESS_USING_CID_ON_NEWER_RECORDS=true

The more complete documentation is in the javadoc of DtlsConfig:

/**
* Update the ip-address from DTLS 1.2 CID records only for newer records
* based on epoch/sequence_number.
*
* @see <a href= "">www.rfc-editor.org/.../rfc9146.html
* target= "_blank">RFC 9146, Connection Identifiers for DTLS 1.2, 6.
* Peer Address Update</a>
*/

In general all CID record will update the address of the DTLS context. (If leshan is using that as well, is out of my scope). But assuming, that records may be received in inverse order, it may cause to update to a deprecated address. This setting therefore updates the address only for the newest record according the dtls record sequence number. In the very, very most cases it doesn't make a difference (because the record order doesn't change that frequently nor will the address change that fast), and it is already on per default.

[quote userid="97896" url="~/f/nordic-q-a/114133/help-with-lte-connection-after-loss-of-connection/507519"]I don't see that `DTLS.CONNECTION_ID_LENGTH` setting in our Leshan server[/quote]

Therefore I recommend to ask the leshan project, how they set that up. For Californium on it's own, it's required, because the default there is for v3. "off".

RE: Help with LTE connection after loss of connection

Matias Marti — Wed, 23 Oct 2024 08:48:07 GMT

Thank you. We will try this.

Now, when the server responds to registration updates immediately, the device keeps running longer.

However, we are consistently seeing that, after almost 50min, the board just restarts itself. See logs:

[00:48:13.524,230] <inf> net_lwm2m_rd_client: Update Done
[00:48:32.525,146] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:48:32.892,547] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:48:32.892,608] <dbg> app_lwm2m_client: rd_client_event: Registration update complete
[00:48:32.892,608] <dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok!
[00:48:32.892,700] <inf> net_lwm2m_rd_client: Update Done
[00:48:51.892,669] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:48:52.323,059] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:48:52.323,089] <dbg> app_lwm2m_client: rd_client_event: Registration update complete
[00:48:52.323,120] <dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok!
[00:48:52.323,211] <inf> net_lwm2m_rd_client: Update Done
[00:49:11.324,127] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:49:11.685,546] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:49:11.685,577] <dbg> app_lwm2m_client: rd_client_event: Registration update complete
[00:49:11.685,607] <dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok!
[00:49:11.685,699] <inf> net_lwm2m_rd_client: Update Done
[00:49:30.685,607] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:49:31.045,043] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:49:31.045,074] <dbg> app_lwm2m_client: rd_client_event: Registration update complete
[00:49:31.045,104] <dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok!
[00:49:31.045,196] <inf> net_lwm2m_rd_client: Update Done
uart:~$ *** Booting nRF Connect SDK v3.5.99-ncs1 ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x1
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0x10000
I: Jumping to the first image slot
*** Booting nRF Connect SDK v3.5.99-ncs1 ***
[00:00:00.255,310] <inf> app_lwm2m_client: Run LWM2M client
[00:00:00.255,371] <dbg> app_lwm2m_client: watchdog_Init: Watchdog started: 0
--- 14 messages dropped ---
[00:00:00.495,605] <inf> app_lwm2m_client: Clearing PSK
[00:00:00.526,641] <dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok!
[00:00:00.805,114] <err> net_lwm2m_registry: obj field 300 not found
[00:00:00.805,297] <err> net_lwm2m_registry: obj field 300 not found
[00:00:00.805,450] <err> net_lwm2m_registry: obj field 300 not found

Could there be something outside of the lwm2m client or anything else that is causing a reboot after 50 min?

Here is our prj.conf file:

# General config
CONFIG_ASSERT=y
CONFIG_REBOOT=y

# Network
CONFIG_NETWORKING=y
CONFIG_NET_NATIVE=n
CONFIG_NET_IPV6=n
CONFIG_NET_IPV4=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_OFFLOAD=y

# Sensors
CONFIG_ADC=y
CONFIG_SPI=y
CONFIG_SPI_NRFX=y
CONFIG_SENSOR=y
CONFIG_I2C=y

# LwM2M and IPSO
CONFIG_LWM2M=y
CONFIG_LWM2M_COAP_BLOCK_SIZE=1024
CONFIG_LWM2M_COAP_MAX_MSG_SIZE=1280
CONFIG_LWM2M_ENGINE_MAX_OBSERVER=40
CONFIG_LWM2M_ENGINE_MAX_MESSAGES=40
CONFIG_LWM2M_ENGINE_MAX_PENDING=40
CONFIG_LWM2M_ENGINE_MAX_REPLIES=40
CONFIG_LWM2M_ENGINE_STACK_SIZE=3072
CONFIG_LWM2M_DNS_SUPPORT=y
CONFIG_LWM2M_RW_JSON_SUPPORT=n
CONFIG_LWM2M_CONN_MON_OBJ_SUPPORT=y
CONFIG_LWM2M_CONN_MON_BEARER_MAX=2
CONFIG_LWM2M_SERVER_DEFAULT_PMIN=0
CONFIG_LWM2M_SERVER_DEFAULT_PMAX=0
CONFIG_LWM2M_CLIENT_UTILS=y
CONFIG_LWM2M_CLIENT_UTILS_FIRMWARE_UPDATE_OBJ_SUPPORT=y
CONFIG_LWM2M_CLIENT_UTILS_LOCATION_OBJ_SUPPORT=n
CONFIG_LWM2M_IPSO_SUPPORT=y


CONFIG_COAP_INIT_ACK_TIMEOUT_MS=4000
CONFIG_COAP_RANDOMIZE_ACK_TIMEOUT=n
CONFIG_COAP_BACKOFF_PERCENT=100
CONFIG_COAP_MAX_RETRANSMIT=4

# UART
CONFIG_UART_INTERRUPT_DRIVEN=y

# DTLS settings
CONFIG_LWM2M_DTLS_SUPPORT=y

# Modem key management
CONFIG_MODEM_KEY_MGMT=y

# Default app to debug logging
CONFIG_LOG=y
CONFIG_APP_LOG_LEVEL_DBG=y
CONFIG_LOG_DEFAULT_LEVEL=3
CONFIG_APP_ENDPOINT_PREFIX="xxx-"

# Support HEX style PSK values (double the size + NULL char)
CONFIG_LWM2M_SECURITY_KEY_SIZE=33

# extend CoAP retry timing to 10 seconds for LTE/LTE-M
CONFIG_COAP_INIT_ACK_TIMEOUT_MS=10000

# Enable CoAP extended option length
CONFIG_COAP_EXTENDED_OPTIONS_LEN=y
CONFIG_COAP_EXTENDED_OPTIONS_LEN_VALUE=40

# Enable settings storage
CONFIG_SETTINGS=y
CONFIG_FCB=y
CONFIG_SETTINGS_FCB=y
CONFIG_FLASH_MAP=y
CONFIG_STREAM_FLASH=y

# LTE link control
CONFIG_LTE_LINK_CONTROL=y
CONFIG_LTE_NETWORK_MODE_LTE_M=y

# Modem library
CONFIG_NRF_MODEM_LIB=y

# Modem info
CONFIG_MODEM_INFO=y
CONFIG_MODEM_INFO_ADD_DATE_TIME=n

# Enable shell
CONFIG_LWM2M_SHELL=y

# Heap and stacks
CONFIG_HEAP_MEM_POOL_SIZE=16384
CONFIG_MAIN_STACK_SIZE=8192
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
CONFIG_AT_MONITOR_HEAP_SIZE=512

# Allow FOTA downloads using download-client
CONFIG_DOWNLOAD_CLIENT=y
CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096
CONFIG_DOWNLOAD_CLIENT_HTTP_FRAG_SIZE_1024=y
CONFIG_FOTA_DOWNLOAD=y

# Application version
CONFIG_MCUBOOT_IMGTOOL_SIGN_VERSION="1.0.0"

# Set LwM2M Server IP address here
CONFIG_LWM2M_CLIENT_UTILS_SERVER="coap://qiotb.qlocx.com:5683"

# Application Event Manager
CONFIG_APP_EVENT_MANAGER=y

# Date-Time library
CONFIG_DATE_TIME=y
CONFIG_DATE_TIME_UPDATE_INTERVAL_SECONDS=86400

# Enable LwM2M Queue Mode
CONFIG_LWM2M_QUEUE_MODE_ENABLED=y

# Use DTLS Connection ID
CONFIG_LWM2M_DTLS_CID=y

CONFIG_LWM2M_RD_CLIENT_SUPPORT_BOOTSTRAP=y
CONFIG_LWM2M_CLIENT_UTILS_BOOTSTRAP_TLS_TAG=100
CONFIG_LWM2M_CLIENT_UTILS_SERVER_TLS_TAG=200

# When DTLS CID is used, we can keep the socket open.
# If the server is not supporting CID, CONFIG_LWM2M_RD_CLIENT_SUSPEND_SOCKET_AT_IDLE should
# be used instead.
CONFIG_LWM2M_RD_CLIENT_STOP_POLLING_AT_IDLE=y

# Enable TLS session caching to prevent doing a full TLS handshake when recovering the session
CONFIG_LWM2M_TLS_SESSION_CACHING=y

# Sets the duration that the lwm2m engine will be polling for data after transmission before
# the socket is closed.
# Adjust so that we can detach from network in 30 seconds
CONFIG_LWM2M_QUEUE_MODE_UPTIME=20

# Set lifetime of 24 hours
CONFIG_LWM2M_ENGINE_DEFAULT_LIFETIME=86400

# This is same as DEFAULT_LIFETIME - QUEUE_MODE_UPTIME + 1
CONFIG_LWM2M_SECONDS_TO_UPDATE_EARLY=86381

# Configure PSM mode
CONFIG_LTE_PSM_REQ=y
# Request periodic TAU of 3600 seconds (60 minutes)
CONFIG_LTE_PSM_REQ_RPTAU="00000110"

# Set Requested Active Time (RAT) to 30 seconds. Preferably same as the
# configured LWM2M_QUEUE_MODE_UPTIME. Due to NAT/firewall UDP connections are usually
# closed within 30-60 seconds so there is in general no point in setting a longer
# Queue mode uptime / LTE PSM active time.
CONFIG_LTE_PSM_REQ_RAT="00001111"

# Request eDRX mode
CONFIG_LTE_EDRX_REQ=y

# Requested eDRX cycle length for LTE-M and Nb-IoT
# This should be fine-tuned for the network and the chosen server.
# Lowest value is  the most responsive, but uses more energy during the active eDRX period.
# Longer period may cause more CoAP packet drops on server requests.
# "0000" is 5.12 s
# "0001" is 10.24 s
# "0010" is 20.48 s.
CONFIG_LTE_EDRX_REQ_VALUE_LTE_M="0001"
CONFIG_LTE_EDRX_REQ_VALUE_NBIOT="0000"

# Request Paging time window of 1.28 seconds for LTE-M
CONFIG_LTE_PTW_VALUE_LTE_M="0000"

# Request Paging time window of 2.56 seconds for NB-IoT
CONFIG_LTE_PTW_VALUE_NBIOT="0000"

# Get notification before Tracking Area Update (TAU). Notification triggers registration
# update and TAU will be sent with the update which decreases power consumption.
CONFIG_LTE_LC_TAU_PRE_WARNING_NOTIFICATIONS=y

CONFIG_PM_DEVICE=y
CONFIG_TFM_LOG_LEVEL_SILENCE=y
# Optimize powersaving by using tickless mode in LwM2M engine
CONFIG_NET_SOCKETPAIR=y
CONFIG_LWM2M_TICKLESS=y
# Enable Release Assistance Indication

#LwM2M v1.1 configure
CONFIG_LWM2M_VERSION_1_1=y
CONFIG_LWM2M_RW_OMA_TLV_SUPPORT=y
CONFIG_LWM2M_COMPOSITE_PATH_LIST_SIZE=20

#Enable SenML-JSON content format
CONFIG_BASE64=y
CONFIG_JSON_LIBRARY=y
CONFIG_LWM2M_RW_SENML_JSON_SUPPORT=y

#Enable SenML-CBOR content format
CONFIG_LWM2M_RW_SENML_CBOR_SUPPORT=y
CONFIG_LWM2M_RW_SENML_CBOR_RECORDS=55
CONFIG_ZCBOR_CANONICAL=y

# Enable below for modem trace
# CONFIG_NRF_MODEM_LIB_TRACE=y
# CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT=y
# CONFIG_USE_SEGGER_RTT=y
#CONFIG_NRF_MODEM_LIB_TRACE_LEVEL_LTE_AND_IP=y

################# WATCHDOG ################################
CONFIG_WDT_LOG_LEVEL_DBG=y
CONFIG_WATCHDOG=y
CONFIG_WDT_DISABLE_AT_BOOT=y

# CONFIG_LWM2M_RD_CLIENT_MAX_RETRIES=

RE: Help with LTE connection after loss of connection

SeppoTakalo — Wed, 23 Oct 2024 08:13:57 GMT

Try:

  # DTLS update address using CID on newer records.
  # Default: true
  DTLS.UPDATE_ADDRESS_USING_CID_ON_NEWER_RECORDS=true

I don't see that `DTLS.CONNECTION_ID_LENGTH` setting in our Leshan server, so maybe it supports it by default, if the client requests Connection-ID.

With the current Leshan, I have not seen any problems with Connection-ID. Even that "UPDATE_ADDRESS" setting seem to be on by default.

You can verify your configuration by running one client against https://leshan.eclipseprojects.io/ it supports DTLS CID and updates client IP when I do LwM2M Update.

RE: Help with LTE connection after loss of connection

Achim Kraus — Tue, 22 Oct 2024 15:24:04 GMT

That ticket is from a time long ago.

During the development of RFC 9146 the MAC calculation has changed pretty late. That caused also the usage of a new Hello Extension ID.

Unfortunately, the mbedtls team wasn't able to adapt and update the implementation in time, therefore to complicated workaround in that old issue.

Today for Californium you only need to enable DTLS 1.2 CID with

# DTLS connection ID length. <blank> disabled, 0 enables support without
# active use of CID.
DTLS.CONNECTION_ID_LENGTH=6

But I'm not sure, what is required for Leshan to handle the address changes in other layers as well. Therefore you maybe open an ticket there.

RE: Help with LTE connection after loss of connection

Matias Marti — Tue, 22 Oct 2024 15:17:42 GMT

Thank you Achim Kraus

Yes, we are using our own Leshan server.

https://github.com/eclipse-leshan/leshan/issues/1166

I read through this issue, and I did not really understand how we would have to modify our Californium.properties file to support CID.

RE: Help with LTE connection after loss of connection

Achim Kraus — Tue, 22 Oct 2024 15:13:56 GMT

[quote userid="133668" url="~/f/nordic-q-a/114133/help-with-lte-connection-after-loss-of-connection/507310"]

It seems like Leshan/Californium does not support DTLS CID.

[/quote]

It's supported in Californium, I added the support pretty early during the development of RFC 9146 (I'm one of the co-authors).

Do you run Leshan on your own? Then you may need to enable CID via the configuration.

Unfortunately, it's not only the DTLS layer, which may get "mixed up" by the NAT changes. So you need also to consider Leshan's other settings to configure it proper (maybe you need to open an ticket/issue in the Leshan project.)

RE: Help with LTE connection after loss of connection

SeppoTakalo — Tue, 22 Oct 2024 13:26:19 GMT

https://en.wikipedia.org/wiki/Network_address_translation#One-to-many_NAT
NAT happens at IP layer.

So in order to keep the current mapping active, you must send UDP packets through in the higher frequency than what the network routers NAT timeout is.

So in a short: There is no way to prevent NAT timeout without sending packets.

If you want to prevent the timeout, you can configure for example CONFIG_LWM2M_UPDATE_PERIOD to be a small enough so that it does not cause NAT timeouts.

I would still recommend to keep the configs from previous example, so if for some reason, the timeout happens, next handshake would still be using session resumption.

There is a risk on that kind of configuration however: If we configure UPDATE_PERIOD shorter than QUEUE_MODE_UPTIME it means that LwM2M engine is never in so called RX_OFF state, or one might call it QUEUE mode. So it assumes that socket is constantly active, and does not try DTLS Session resumption.
If we end up sending LwM2M Update message into DTLS socket where NAT timeout have happened, it causes all DTLS packets to be ignore by the server. And then all the CoAP retry logic is just wasted time.

If we instead assume that NAT timeouts might happen, and allow those to happen, and configure UPDATE_PERIOD to a longer value, for example several minutes or hours, then LwM2M Update causes engine to "resume" the DTLS connection, which means that it actually closes the socket and does a new handshake using DTLS Session resumption. This is almost like full DTLS-handshake but shorter. It is accepted by the server because it starts with normal DTLS Client-Hello.

So any approach you take will consume a lot of bandwidth to keep the connection up.

With DTLS Connection-Identifier you get rid of the issues with NAT timeouts because server side uses CID to identify connections instead of IP&port pair. Then NAT re-mapping does not interrupt the DTLS session, it only block the server from communicating to the device, until it does LwM2M Update which refreshes the IP&port mapping.

RE: Help with LTE connection after loss of connection

Matias Marti — Tue, 22 Oct 2024 12:58:53 GMT

SeppoTakalo thanks again.

Is there another way to prevent a NAT timeout? By setting CONFIG_LWM2M_QUEUE_MODE_UPTIME=15 we are using all the layers of communication here below, right?

On which of these layers does the NAT timeout occur? Is there a way to use your SDK so that it sends a message to the LTE network on the lowest possible layer? We would like to prevent NAT timeout without communicating all the way to the Leshan server.

Any thoughts?

RE: Help with LTE connection after loss of connection

SeppoTakalo — Tue, 22 Oct 2024 12:33:20 GMT

Then if the DTLS CID is not enabled in the server side, it might cause these connection issues.

When NAT timeout to happens, the IP&PORT pair mapping will change and it causes Leshan to ignore the LwM2M update messages because they come from unknown port. This offcourse only happens, if LwM2M engine is not instructed to do a DTLS Session resumption when doing a LwM2M Update.

My first recommendation would be to update Leshan, but with current environment, try:

# Do a DTLS Session resumption when coming
# back from RX_OFF state.
CONFIG_LWM2M_RD_CLIENT_SUSPEND_SOCKET_AT_IDLE=y
CONFIG_LWM2M_TLS_SESSION_CACHING=y

# Fine-tune the timeout to match NAT timeout on
# current network. I have seen 20s on some LTE networks in Finland.
# Try 10, 15, 20, 30
CONFIG_LWM2M_QUEUE_MODE_ENABLED=y
CONFIG_LWM2M_QUEUE_MODE_UPTIME=15

RE: Help with LTE connection after loss of connection

Matias Marti — Tue, 22 Oct 2024 11:34:21 GMT

[00:00:17.177,490] <inf> app_lwm2m_client: LwM2M is connected to server
[00:00:17.177,551] <inf> app_lwm2m_client: Obtained date-time from modem
[00:00:36.092,285] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:01:16.382,965] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:01:16.383,026] <dbg> app_lwm2m_client: rd_client_event: Registration update complete
[00:01:16.383,056] <dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok!
[00:01:16.383,148] <inf> net_lwm2m_rd_client: Update Done
[00:01:35.383,056] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:02:15.828,491] <inf> net_lwm2m_rd_client: Update callback (code:2.4)
[00:02:15.828,552] <dbg> app_lwm2m_client: rd_client_event: Registration update complete
[00:02:15.828,582] <dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok!
[00:02:15.828,643] <inf> net_lwm2m_rd_client: Update Done

It takes up to 40s for the registration update to complete when we set these config values:

CONFIG_COAP_RANDOMIZE_ACK_TIMEOUT=n
CONFIG_COAP_BACKOFF_PERCENT=100
CONFIG_COAP_MAX_RETRANSMIT=4

We are also getting the following logs:

[00:02:31.944,396] <dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok!
[00:02:31.944,488] <inf> net_lwm2m_rd_client: Update Done
[00:02:32.430,450] <dbg> app_lwm2m_client: rd_client_event: Queue mode RX window closed
[00:02:50.944,335] <dbg> app_lwm2m_client: rd_client_event: Registration update started

When the server is slow to respond after an initial registration update, it seems like the queue mode RX gets closed right before the next registration update starts. Could this be some sort of race condition?

When our Leshan server responds, the logs just stay quiet until the watchdog kicks in.

RE: Help with LTE connection after loss of connection

Matias Marti — Tue, 22 Oct 2024 10:45:05 GMT

SeppoTakalo Thank you.

It seems like Leshan/Californium does not support DTLS CID.

When using the following flags, we get the following application logs:

CONFIG_COAP_INIT_ACK_TIMEOUT_MS=4000
CONFIG_COAP_RANDOMIZE_ACK_TIMEOUT=n
CONFIG_COAP_BACKOFF_PERCENT=100
CONFIG_COAP_MAX_RETRANSMIT=4

[00:04:26.741,607] <inf> app_lwm2m_client: LwM2M is connected to server
[00:04:26.741,668] <inf> app_lwm2m_client: Obtained date-time from modem
[00:04:45.655,761] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:05:05.756,042] <wrn> net_lwm2m_rd_client: Registration Update Timeout
[00:05:05.756,164] <dbg> app_lwm2m_client: rd_client_event: Registration update failure!
[00:05:05.758,117] <inf> net_lwm2m_rd_client: RD Client started with endpoint '<MY_ENDPOINT>' with client lifetime 86400 using server object 0
[00:05:05.877,807] <inf> app_lwm2m_client: LwM2M is connecting to server

And these are the Wireshark logs:

499	32.459415	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	89	Application Data
500	43.816044	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	95	Application Data
501	43.948368			LTE RRC DL_DCCH	26	RRCConnectionRelease [cause=other]
502	45.203037			AT	23	Rcvd AT Command: +CSCON: 0  
503	45.203159			AT	31	Rcvd AT Command: %XT3412: 10799999  
504	45.237064			LTE RRC DL_SCH	60	SystemInformationBlockType1
505	45.237614			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
506	45.237797			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
507	53.817081			NAS-EPS	20	Service request
508	53.817997			LTE RRC UL_CCCH	30	RRCConnectionRequest
509	53.900516			LTE RRC DL_CCCH	71	RRCConnectionSetup
510	53.901462			LTE RRC UL_DCCH/NAS-EPS	33	RRCConnectionSetupComplete, Service request
511	53.902927			AT	24	Rcvd AT Command: %XT3412: 0  
512	53.903049			AT	23	Rcvd AT Command: +CSCON: 1  
513	53.986545			LTE RRC DL_DCCH	27	SecurityModeCommand
514	53.988376			LTE RRC UL_DCCH	26	SecurityModeComplete
515	53.995548			LTE RRC DL_DCCH	53	RRCConnectionReconfiguration
516	53.996464			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
517	53.996799	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	95	Application Data
518	54.045505			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
519	54.045841			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
520	63.816746	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	95	Application Data
521	63.948643			LTE RRC DL_DCCH	26	RRCConnectionRelease [cause=other]
522	65.202518			AT	23	Rcvd AT Command: +CSCON: 0  
523	65.202640			AT	31	Rcvd AT Command: %XT3412: 10799999  
524	65.237552			LTE RRC DL_SCH	60	SystemInformationBlockType1
525	65.238102			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
526	65.238285			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
527	73.816990			NAS-EPS	20	Service request
528	73.817936			LTE RRC UL_CCCH	30	RRCConnectionRequest
529	73.901005			LTE RRC DL_CCCH	71	RRCConnectionSetup
530	73.901951			LTE RRC UL_DCCH/NAS-EPS	33	RRCConnectionSetupComplete, Service request
531	73.985020			LTE RRC DL_DCCH	27	SecurityModeCommand
532	73.986759			LTE RRC UL_DCCH	26	SecurityModeComplete
533	73.994053			LTE RRC DL_DCCH	53	RRCConnectionReconfiguration
534	73.994999			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
535	73.995334	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	95	Application Data
536	74.045994			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
537	74.046329			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
538	83.810642	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	95	Application Data
539	93.817447	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	71	Encrypted Alert
540	93.818241			AT	20	Sent AT Command: AT+CMEE?
541	93.818271			AT	26	Rcvd AT Command: +CMEE: 0  OK  
542	93.818851			AT	21	Sent AT Command: AT+CMEE=1
543	93.818882			AT	16	Rcvd AT Command: OK  
544	93.819523			AT	19	Sent AT Command: AT%CMNG
545	93.849064			AT	21	Rcvd AT Command: Sensitive
546	93.849552			AT	21	Sent AT Command: AT+CMEE=0
547	93.849552			AT	16	Rcvd AT Command: OK  
548	93.849979			AT	20	Sent AT Command: AT+CMEE?
549	93.850010			AT	26	Rcvd AT Command: +CMEE: 0  OK  
550	93.850406			AT	21	Sent AT Command: AT+CMEE=1
551	93.850437			AT	16	Rcvd AT Command: OK  
552	93.850864			AT	19	Sent AT Command: AT%CMNG
553	93.880253			AT	21	Rcvd AT Command: Sensitive
554	93.880741			AT	21	Sent AT Command: AT+CMEE=0
555	93.880741			AT	16	Rcvd AT Command: OK  
556	93.881168			AT	20	Sent AT Command: AT+CMEE?
557	93.881199			AT	26	Rcvd AT Command: +CMEE: 0  OK  
558	93.887760			AT	21	Sent AT Command: AT+CMEE=1
559	93.887791			AT	16	Rcvd AT Command: OK  
560	93.888187			AT	19	Sent AT Command: AT%CMNG
561	93.917606			AT	21	Rcvd AT Command: Sensitive
562	93.918094			AT	21	Sent AT Command: AT+CMEE=0
563	93.918094			AT	16	Rcvd AT Command: OK  
564	93.918522			AT	20	Sent AT Command: AT+CMEE?
565	93.918522			AT	26	Rcvd AT Command: +CMEE: 0  OK  
566	93.918979			AT	21	Sent AT Command: AT+CMEE=1
567	93.919010			AT	16	Rcvd AT Command: OK  
568	93.919437			AT	19	Sent AT Command: AT%CMNG
569	93.949375			LTE RRC DL_DCCH	26	RRCConnectionRelease [cause=other]
570	93.954288			AT	21	Rcvd AT Command: Sensitive
571	93.954716			AT	21	Sent AT Command: AT+CMEE=0
572	93.954746			AT	16	Rcvd AT Command: OK  
573	95.203281			AT	23	Rcvd AT Command: +CSCON: 0  
574	95.203403			AT	31	Rcvd AT Command: %XT3412: 10799999  
575	95.238285			LTE RRC DL_SCH	60	SystemInformationBlockType1
576	95.238834			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
577	95.239048			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
578	95.240787			NAS-EPS	20	Service request
579	95.249241			LTE RRC UL_CCCH	30	RRCConnectionRequest
580	95.280521			LTE RRC DL_CCCH	71	RRCConnectionSetup
581	95.281467			LTE RRC UL_DCCH/NAS-EPS	33	RRCConnectionSetupComplete, Service request
582	95.303531			AT	24	Rcvd AT Command: %XT3412: 0  
583	95.340549			LTE RRC DL_DCCH	27	SecurityModeCommand
584	95.342289			LTE RRC UL_DCCH	26	SecurityModeComplete
585	95.349552			LTE RRC DL_DCCH	53	RRCConnectionReconfiguration
586	95.350498			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
587	95.350864	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	170	Client Hello
588	95.350986	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	170	Client Hello
589	95.403690			AT	23	Rcvd AT Command: +CSCON: 1  
590	95.417606			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
591	95.417942			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
592	95.434482	<REMOTE_IP>	<LOCAL_IP>	DTLSv1.2	81	Application Data
593	95.434635	<LOCAL_IP>	<REMOTE_IP>	ICMP	68	Destination unreachable (Port unreachable)
594	95.483524	<REMOTE_IP>	<LOCAL_IP>	DTLSv1.2	202	Server Hello, Change Cipher Spec, Encrypted Handshake Message
595	95.490848	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	107	Change Cipher Spec, Encrypted Handshake Message
596	95.495365	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	605	Application Data
597	95.496586	<LOCAL_IP>	<REMOTE_IP>	DTLSv1.2	71	Encrypted Alert
598	95.603916			AT	20	Sent AT Command: AT+CMEE?
599	95.603947			AT	26	Rcvd AT Command: +CMEE: 0  OK  
600	95.604496			AT	21	Sent AT Command: AT+CMEE=1
601	95.604526			AT	16	Rcvd AT Command: OK  
602	95.604923			AT	19	Sent AT Command: AT%CMNG
603	95.646122			AT	21	Rcvd AT Command: Sensitive
604	95.646763			AT	21	Sent AT Command: AT+CMEE=0
605	95.646793			AT	16	Rcvd AT Command: OK  
606	95.647129			AT	20	Sent AT Command: AT+CMEE?
607	95.647159			AT	26	Rcvd AT Command: +CMEE: 0  OK  
608	95.647770			AT	21	Sent AT Command: AT+CMEE=1
609	95.647800			AT	16	Rcvd AT Command: OK  
610	95.648441			AT	19	Sent AT Command: AT%CMNG
611	95.651462	<REMOTE_IP>	<LOCAL_IP>	DTLSv1.2	71	Encrypted Alert
612	95.651645	<LOCAL_IP>	<REMOTE_IP>	ICMP	68	Destination unreachable (Port unreachable)
613	95.689792			AT	21	Rcvd AT Command: Sensitive
614	95.690525			AT	21	Sent AT Command: AT+CMEE=0
615	95.690525			AT	16	Rcvd AT Command: OK

However, when we set CONFIG_COAP_INIT_ACK_TIMEOUT_MS=10000 , the board manages to perform registration updates, whereas it fails constantly when the value is set to 4000. What would be next step forward?

RE: Help with LTE connection after loss of connection

SeppoTakalo — Wed, 16 Oct 2024 11:03:10 GMT

Also, if you insist that registration message (and update) should have shorter CoAP timeout, you can try modifying the code to set that:

❯ git diff
  diff --git a/subsys/net/lib/lwm2m/lwm2m_rd_client.c b/subsys/net/lib/lwm2m/lwm2m_rd_client.c
  index 22ce51e5248..6da8bac18db 100644
  --- a/subsys/net/lib/lwm2m/lwm2m_rd_client.c
  +++ b/subsys/net/lib/lwm2m/lwm2m_rd_client.c
  @@ -865,6 +865,12 @@ static int sm_send_registration(bool send_obj_support_data,
                  goto cleanup;
          }
   
  +       msg->pending->params = (struct coap_transmission_parameters) {
  +               .ack_timeout = 1000,
  +               .coap_backoff_percent = 100,
  +               .max_retransmission = CONFIG_LWM2M_RD_CLIENT_MAX_RETRIES,
  +       };
  +
          ret = coap_packet_append_option(&msg->cpkt, COAP_OPTION_URI_PATH,
                                          LWM2M_RD_CLIENT_URI,
                                          strlen(LWM2M_RD_CLIENT_URI));

but I don't really recommend that. One set of CoAP configuration should work for the whole layer, once it is tuned to work for the given connection.

RE: Help with LTE connection after loss of connection

SeppoTakalo — Tue, 15 Oct 2024 06:50:18 GMT

Try three things:

First, cherry-pick the fix https://github.com/nrfconnect/sdk-nrf/pull/15338 so it does not stop & start the client, but instead allows it to recover normally.

Then modify CoAP timeouts, so that it retries a bit faster and does not back-off so much

CONFIG_COAP_INIT_ACK_TIMEOUT_MS=4000
CONFIG_COAP_RANDOMIZE_ACK_TIMEOUT=n
CONFIG_COAP_BACKOFF_PERCENT=100
CONFIG_COAP_MAX_RETRANSMIT=4

Then, I have not seen verification whether the DTLS Connection-Identifier is used.
Make sure that the Kconfig is set:

CONFIG_LWM2M_DTLS_CID=y

Then verify from the Wireshark capture that it is in fact enabled. This requires support form server side as well.

RE: Help with LTE connection after loss of connection

Matias Marti — Mon, 14 Oct 2024 15:04:51 GMT

Thank you. It is great that the client recovers from an update timeout. However, our Leshan server considers the device to have fallen asleep if there has been no messages for 93s. How can we make sure that Leshan does not have to wait for the 4min7s (timeout)?

Which COAP config value should we change to trigger a timeout earlier than 247s?

RE: Help with LTE connection after loss of connection

SeppoTakalo — Mon, 14 Oct 2024 13:28:39 GMT

I also tried to replicate this behaviour on nRF9160DK and with nRF Connect SDK 2.6.0. In order to cause the problem, I had to turn off the DTLS Connection-Identifier so NAT timeout will happen.

I think I found something which I just saw on your logs.

uart:~$ lwm2m update
[00:03:21.185,638] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:06:20.157,104] <wrn> net_lwm2m_rd_client: Registration Update Timeout
[00:06:20.157,226] <inf> lwm2m_rai: RAI disabled
[00:06:20.157,257] <dbg> app_lwm2m_client: rd_client_event: Registration update failure!
[00:06:20.166,778] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:351358814369747' with client lifetime 43200 using server object 0
[00:06:21.534,088] <inf> net_lwm2m_engine: Connected, sock id 2
[00:06:21.536,285] <dbg> app_lwm2m_client: rd_client_event: Disconnected
[00:06:21.536,407] <inf> net_lwm2m_rd_client: Stop LWM2M Client: urn:imei:351358814369747
[00:06:21.622,833] <inf> app_lwm2m_client: Client connect to server
[00:06:21.622,894] <inf> net_lwm2m_rd_client: Start LWM2M Client: urn:imei:351358814369747
[00:06:21.623,443] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:351358814369747' with client lifetime 43200 using server object 0
[00:06:21.748,229] <inf> app_lwm2m_client: LwM2M is connecting to server
[00:06:22.174,072] <inf> net_lwm2m_engine: Connected, sock id 2
[00:06:22.270,721] <dbg> app_lwm2m_client: rd_client_event: Registration complete
[00:06:22.270,874] <inf> net_lwm2m_rd_client: Registration Done (EP='rxUng0f9N8')

There is no reason to stop the client.
This has been fixed in https://github.com/nrfconnect/sdk-nrf/pull/15338

LwM2M client recovers from update timeout.

Here is a log of the 2.6.0 + the fix

uart:~$ lwm2m update
[00:01:19.919,128] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:04:22.022,033] <wrn> net_lwm2m_rd_client: Registration Update Timeout
[00:04:22.022,155] <inf> lwm2m_rai: RAI disabled
[00:04:22.022,155] <dbg> app_lwm2m_client: rd_client_event: Registration update failure!
[00:04:22.030,853] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'urn:imei:351358814369747' with client lifetime 43200 using server object 0
[00:04:22.169,616] <inf> app_lwm2m_client: LwM2M is connecting to server
[00:04:23.408,752] <inf> net_lwm2m_engine: Connected, sock id 2
[00:04:23.501,373] <dbg> app_lwm2m_client: rd_client_event: Registration complete
[00:04:23.501,495] <inf> net_lwm2m_rd_client: Registration Done (EP='G2ut7hCAmu')
[00:04:23.587,158] <inf> app_lwm2m_client: LwM2M is connected to server
[00:04:23.587,219] <inf> app_lwm2m_client: Obtained date-time from modem
[00:04:53.411,499] <inf> lwm2m_rai: RAI enabled
[00:04:53.411,529] <dbg> app_lwm2m_client: rd_client_event: Queue mode RX window closed

devzone.nordicsemi.com/.../2024_2D00_10_2D00_14-nRF9160-LwM2M-Update-failure_2C00_-NAT-timeout.pcapng devzone.nordicsemi.com/.../2024_2D00_10_2D00_14-nRF9160-LwM2M-Update-failure_2C00_-NAT-timeout-plus-fix.pcapng

I'll try to attach the wireshark captures for you to check if this is the behaviour that you are seeing. PSK key is e0e7f1368e66c05f3511b5fa4671f56e

RE: Help with LTE connection after loss of connection

SeppoTakalo — Mon, 14 Oct 2024 12:45:15 GMT

I cannot replicate this "stuck for 4min7s" issue.

When I run nRF Connect SDK with unmodified lwm2m_client.c in zephyr/samples/net, build in native_sim, this is the behaviour:

92 seconds of retries, then fallback to full registration.

Here is the application log

[00:00:00.510,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 1
[00:00:00.510,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 6
[00:00:00.510,000] <dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0xeecfc19c, buflen:4
[00:00:00.510,000] <dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/0/0, level 3, buf:0xeecfc1de, buflen:2
[00:00:00.510,000] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'native_sim' with client lifetime 30 using server object 0
[00:00:00.510,000] <dbg> net_lwm2m_message_handling: lwm2m_parse_peerinfo: Parse url: coap://192.0.2.2:5683
[00:00:00.510,000] <inf> net_lwm2m_engine: Connected, sock id 0
[00:00:00.510,000] <dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0xeecfc14c, buflen:4
[00:00:00.510,000] <dbg> net_lwm2m_rd_client: sm_send_registration: registration sent [192.0.2.2]
[00:00:00.510,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 8
[00:00:00.510,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_ONE_RESPONSE
[00:00:00.600,000] <dbg> net_lwm2m_rd_client: do_registration_reply_cb: Registration callback (code:2.1)
[00:00:00.600,000] <dbg> net_lwm2m_client_app: rd_client_event: Registration complete
[00:00:00.600,000] <inf> net_lwm2m_rd_client: Registration Done (EP='HsVT6yWrkF')
[00:00:00.600,000] <dbg> net_lwm2m_message_handling: lwm2m_udp_receive: reply 0x808cd68 handled and removed
[00:00:00.600,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_NO_DATA
[00:00:00.600,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 9
uart:~$ lwm2m update
[00:00:20.530,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 9
[00:00:20.530,000] <dbg> net_lwm2m_client_app: rd_client_event: Registration update
[00:00:20.640,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 11
[00:00:20.640,000] <dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0xeecfc15c, buflen:4
[00:00:20.640,000] <dbg> net_lwm2m_rd_client: sm_send_registration: registration sent [192.0.2.2]
[00:00:20.640,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 12
[00:00:20.640,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_ONE_RESPONSE
[00:00:23.620,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_ONE_RESPONSE
[00:00:29.540,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_ONE_RESPONSE
[00:00:41.400,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_ONE_RESPONSE
[00:01:05.100,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_ONE_RESPONSE
[00:01:52.510,000] <wrn> net_lwm2m_rd_client: Registration Update Timeout
[00:01:52.510,000] <dbg> net_lwm2m_client_app: rd_client_event: Registration timeout!
[00:01:53.020,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 6
[00:01:53.020,000] <dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0xeecfc19c, buflen:4
[00:01:53.020,000] <dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/0/0, level 3, buf:0xeecfc1de, buflen:2
[00:01:53.020,000] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'native_sim' with client lifetime 30 using server object 0
[00:01:53.020,000] <dbg> net_lwm2m_message_handling: lwm2m_parse_peerinfo: Parse url: coap://192.0.2.2:5683
[00:01:53.020,000] <inf> net_lwm2m_engine: Connected, sock id 0
[00:01:53.020,000] <dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0xeecfc14c, buflen:4
[00:01:53.020,000] <dbg> net_lwm2m_rd_client: sm_send_registration: registration sent [192.0.2.2]
[00:01:53.020,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 8
[00:01:53.020,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_ONE_RESPONSE
[00:01:55.400,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_ONE_RESPONSE
[00:02:00.120,000] <dbg> net_lwm2m_registry: lwm2m_engine_set: path:3303/0/5700, buf:0xf04ff1f8, len:8
[00:02:00.140,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_ONE_RESPONSE
[00:02:00.240,000] <dbg> net_lwm2m_rd_client: do_registration_reply_cb: Registration callback (code:2.1)
[00:02:00.240,000] <dbg> net_lwm2m_client_app: rd_client_event: Registration complete
[00:02:00.240,000] <inf> net_lwm2m_rd_client: Registration Done (EP='Qf5sCfKOzy')
[00:02:00.240,000] <dbg> net_lwm2m_message_handling: lwm2m_udp_receive: reply 0x808cd68 handled and removed
[00:02:00.240,000] <dbg> net_lwm2m_client_app: socket_state: LWM2M_SOCKET_STATE_NO_DATA
[00:02:00.240,000] <dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 9
uart:~$

Notice that there is even the application event:

> [00:01:52.510,000] <wrn> net_lwm2m_rd_client: Registration Update Timeout

Behaviour is pretty much the same when DTLS is used. It just re-starts the DTLS handshake before registration starts.

So I don't think I have seen the real root cause that gets devices disconnected.

RE: Help with LTE connection after loss of connection

Matias Marti — Mon, 14 Oct 2024 10:55:14 GMT

To answer the first question:

These logs are the Wireshark logs that are generated by our device when it tries to communicate with a Leshan server that we decide to make unavailable. These are not Leshan logs. We are stopping the Leshan server in order to see how the board behaves, including what the Wireshark logs tell us.

Second question:

The problem we are trying to fix is that the board should be able to handle a scenario during which the registration update "gets stuck" for 4min7s. Because the request is pending for so long, we do not get a LWM2M_RD_CLIENT_EVENT_REG_UPDATE_COMPLETE (which in turn is supposed to perform a watchdog kick) in time, which ends up with the watchdog causing an unnecessary reboot.

RE: Help with LTE connection after loss of connection

dejans — Mon, 14 Oct 2024 09:38:26 GMT

Hi,

Are both of these code snippets part of the same log from the server?
Is log taken when everything was working as expected?

[quote user="SeppoTakalo"]

Have you checked with Wireshark what is exactly happening if you do this?

What problem do you expect this to fix?

[/quote]

Matias Marti Could you provide answers to these questions?

Best regards,
Dejan

RE: Help with LTE connection after loss of connection

Matias Marti — Thu, 10 Oct 2024 10:58:50 GMT

My bad. I forgot about using Wireshark this time.

Here are the last logs before we stop the Leshan server:

547	110.376831			                 LTE RRC DL_DCCH	53	RRCConnectionReconfiguration
548	110.377746				             LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
549	110.378113	<LOCAL_IP>	<LESHAN_IP>	 DTLSv1.2	        95	Application Data
550	110.437866		                     LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
551	110.438202	    	                 LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
552	118.979034						     AT	                30	Rcvd AT Command: %CESQ: 61,3,16,2

And here below is the rest of the logs. Around entry 601 (ca 250s after the last registration update), is when the pending registration update fails. A bit after entry 620 is when the watchdog triggers a restart, which is followed by a bootstrapping by our bootstrap server.

552	118.979034			AT	30	Rcvd AT Command: %CESQ: 61,3,16,2  
553	120.293121			LTE RRC DL_DCCH	26	RRCConnectionRelease [cause=other]
554	121.547973			AT	23	Rcvd AT Command: +CSCON: 0  
555	121.548096			AT	31	Rcvd AT Command: %XT3412: 10799999  
556	121.564850			LTE RRC DL_SCH	60	SystemInformationBlockType1
557	121.565399			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
558	121.565582			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
559	127.704376			AT	30	Rcvd AT Command: %CESQ: 61,3,11,1  
560	137.588409			NAS-EPS	20	Service request
561	137.589355			LTE RRC UL_CCCH	30	RRCConnectionRequest
562	137.667480			LTE RRC DL_CCCH	71	RRCConnectionSetup
563	137.668457			LTE RRC UL_DCCH/NAS-EPS	33	RRCConnectionSetupComplete, Service request
564	137.669952			AT	24	Rcvd AT Command: %XT3412: 0  
565	137.670074			AT	23	Rcvd AT Command: +CSCON: 1  
566	137.729492			LTE RRC DL_DCCH	27	SecurityModeCommand
567	137.731293			LTE RRC UL_DCCH	26	SecurityModeComplete
568	137.738525			LTE RRC DL_DCCH	53	RRCConnectionReconfiguration
569	137.739471			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
570	137.739807	<LOCAL_IP>	<LESHAN_IP>	DTLSv1.2	95	Application Data
571	137.801575			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
572	137.801880			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
573	145.499725			AT	30	Rcvd AT Command: %CESQ: 62,3,16,2  
574	147.741821			LTE RRC DL_DCCH	26	RRCConnectionRelease [cause=other]
575	148.994293			AT	23	Rcvd AT Command: +CSCON: 0  
576	148.994415			AT	31	Rcvd AT Command: %XT3412: 10799999  
577	149.065552			LTE RRC DL_SCH	60	SystemInformationBlockType1
578	149.066101			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
579	149.066284			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
580	192.408386			NAS-EPS	20	Service request
581	192.409332			LTE RRC UL_CCCH	30	RRCConnectionRequest
582	192.489898			LTE RRC DL_CCCH	71	RRCConnectionSetup
583	192.490845			LTE RRC UL_DCCH/NAS-EPS	33	RRCConnectionSetupComplete, Service request
584	192.492340			AT	24	Rcvd AT Command: %XT3412: 0  
585	192.492462			AT	23	Rcvd AT Command: +CSCON: 1  
586	192.541931			LTE RRC DL_DCCH	27	SecurityModeCommand
587	192.543732			LTE RRC UL_DCCH	26	SecurityModeComplete
588	192.550934			LTE RRC DL_DCCH	53	RRCConnectionReconfiguration
589	192.551880			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
590	192.552215	<LOCAL_IP>	<LESHAN_IP>	DTLSv1.2	95	Application Data
591	192.593933			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
592	192.594238			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
593	202.591217			LTE RRC DL_DCCH	26	RRCConnectionRelease [cause=other]
594	203.843689			AT	23	Rcvd AT Command: +CSCON: 0  
595	203.843780			AT	31	Rcvd AT Command: %XT3412: 10799999  
596	203.946960			LTE RRC DL_SCH	60	SystemInformationBlockType1
597	203.947510			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
598	203.947693			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
599	205.786377			AT	30	Rcvd AT Command: %CESQ: 64,3,11,1  
600	302.048248			NAS-EPS	20	Service request
601	302.049194			LTE RRC UL_CCCH	30	RRCConnectionRequest
602	302.132690			LTE RRC DL_CCCH	71	RRCConnectionSetup
603	302.133667			LTE RRC UL_DCCH/NAS-EPS	33	RRCConnectionSetupComplete, Service request
604	302.135132			AT	24	Rcvd AT Command: %XT3412: 0  
605	302.135254			AT	23	Rcvd AT Command: +CSCON: 1  
606	302.215668			LTE RRC DL_DCCH	27	SecurityModeCommand
607	302.217499			LTE RRC UL_DCCH	26	SecurityModeComplete
608	302.224701			LTE RRC DL_DCCH	53	RRCConnectionReconfiguration
609	302.225647			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
610	302.226013	<LOCAL_IP>	<LESHAN_IP>	DTLSv1.2	95	Application Data
611	302.269745			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
612	302.270050			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
613	312.208038			LTE RRC DL_DCCH	26	RRCConnectionRelease [cause=other]
614	312.519958			AT	30	Rcvd AT Command: %CESQ: 62,3,16,2  
615	313.460754			AT	23	Rcvd AT Command: +CSCON: 0  
616	313.460876			AT	31	Rcvd AT Command: %XT3412: 10799999  
617	313.549743			LTE RRC DL_SCH	60	SystemInformationBlockType1
618	313.550293			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
619	313.550476			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
620	329.949554			AT	30	Rcvd AT Command: %CESQ: 64,3,11,1  
621	343.474029			NAS-EPS	20	Service request
622	343.474365			AT	20	Sent AT Command: AT+CMEE?
623	343.474365			AT	26	Rcvd AT Command: +CMEE: 0  OK  
624	343.475311			AT	21	Sent AT Command: AT+CMEE=1
625	343.475342			AT	16	Rcvd AT Command: OK  
626	343.475738			AT	19	Sent AT Command: AT%CMNG
627	343.487915			LTE RRC UL_CCCH	30	RRCConnectionRequest
628	343.506561			AT	21	Rcvd AT Command: Sensitive
629	343.507049			AT	21	Sent AT Command: AT+CMEE=0
630	343.507080			AT	16	Rcvd AT Command: OK  
631	343.507477			AT	20	Sent AT Command: AT+CMEE?
632	343.507507			AT	26	Rcvd AT Command: +CMEE: 0  OK  
633	343.507965			AT	21	Sent AT Command: AT+CMEE=1
634	343.507995			AT	16	Rcvd AT Command: OK  
635	343.508606			AT	19	Sent AT Command: AT%CMNG
636	343.541321			AT	21	Rcvd AT Command: Sensitive
637	343.541748			AT	21	Sent AT Command: AT+CMEE=0
638	343.541778			AT	16	Rcvd AT Command: OK  
639	343.542267			AT	20	Sent AT Command: AT+CMEE?
640	343.542297			AT	26	Rcvd AT Command: +CMEE: 0  OK  
641	343.542724			AT	21	Sent AT Command: AT+CMEE=1
642	343.542755			AT	16	Rcvd AT Command: OK  
643	343.543701			AT	19	Sent AT Command: AT%CMNG
644	343.573761			LTE RRC DL_CCCH	71	RRCConnectionSetup
645	343.574707			LTE RRC UL_DCCH/NAS-EPS	33	RRCConnectionSetupComplete, Service request
646	343.586059			AT	21	Rcvd AT Command: Sensitive
647	343.586181			AT	24	Rcvd AT Command: %XT3412: 0  
648	343.586304			AT	23	Rcvd AT Command: +CSCON: 1  
649	343.586883			AT	21	Sent AT Command: AT+CMEE=0
650	343.586914			AT	16	Rcvd AT Command: OK  
651	343.587585			AT	20	Sent AT Command: AT+CMEE?
652	343.587616			AT	26	Rcvd AT Command: +CMEE: 0  OK  
653	343.588043			AT	21	Sent AT Command: AT+CMEE=1
654	343.588043			AT	16	Rcvd AT Command: OK  
655	343.588684			AT	19	Sent AT Command: AT%CMNG
656	343.628876			AT	21	Rcvd AT Command: Sensitive
657	343.629791			AT	21	Sent AT Command: AT+CMEE=0
658	343.629822			AT	16	Rcvd AT Command: OK  
659	343.653778			LTE RRC DL_DCCH	27	SecurityModeCommand
660	343.655609			LTE RRC UL_DCCH	26	SecurityModeComplete
661	343.662750			LTE RRC DL_DCCH	53	RRCConnectionReconfiguration
662	343.663696			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
663	343.664062	<LOCAL_IP>	<LESHAN_IP>	DTLSv1.2	71	Encrypted Alert
664	343.664154	<LOCAL_IP>	<LESHAN_IP>	DTLS	170	Client Hello
665	343.719787			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
666	343.720123			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
667	344.734955	<LOCAL_IP>	<LESHAN_IP>	DTLS	170	Client Hello
668	345.824829			AT	30	Rcvd AT Command: %CESQ: 61,3,16,2  
669	346.835632	<LOCAL_IP>	<LESHAN_IP>	DTLS	170	Client Hello
670	350.936279	<LOCAL_IP>	<LESHAN_IP>	DTLS	170	Client Hello
671	359.037231	<LOCAL_IP>	<LESHAN_IP>	DTLS	170	Client Hello
672	369.827514			LTE RRC DL_DCCH	26	RRCConnectionRelease [cause=other]
673	371.080292			AT	23	Rcvd AT Command: +CSCON: 0  
674	371.080414			AT	31	Rcvd AT Command: %XT3412: 10799999  
675	371.151214			LTE RRC DL_SCH	60	SystemInformationBlockType1
676	371.151764			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
677	371.151947			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
678	375.138611			NAS-EPS	20	Service request
679	375.152435			LTE RRC UL_CCCH	30	RRCConnectionRequest
680	375.214569			LTE RRC DL_CCCH	71	RRCConnectionSetup
681	375.215515			LTE RRC UL_DCCH/NAS-EPS	33	RRCConnectionSetupComplete, Service request
682	375.216980			AT	24	Rcvd AT Command: %XT3412: 0  
683	375.217071			AT	23	Rcvd AT Command: +CSCON: 1  
684	375.336548			LTE RRC DL_DCCH	27	SecurityModeCommand
685	375.338348			LTE RRC UL_DCCH	26	SecurityModeComplete
686	375.345581			LTE RRC DL_DCCH	53	RRCConnectionReconfiguration
687	375.346527			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
688	375.346863	<LOCAL_IP>	<LESHAN_IP>	DTLS	170	Client Hello
689	375.392608			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
690	375.392944			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
691	378.504019			AT	30	Sent AT Command: AT%XMODEMTRACE=1,2
692	378.504812			AT	16	Rcvd AT Command: OK  
693	378.505514			AT	34	Sent AT Command: AT%XSYSTEMMODE=1,0,0,0
694	378.507193			AT	16	Rcvd AT Command: OK  
695	378.507589			AT	46	Sent AT Command: AT+CPSMS=1,,,"00000110","00001111"
696	378.507711			AT	16	Rcvd AT Command: OK  
697	378.508261			AT	19	Rcvd AT Command: ERROR  
698	378.508657			AT	32	Sent AT Command: AT+CEDRXS=2,4,"0001"
699	378.508749			AT	16	Rcvd AT Command: OK  
700	378.509146			AT	28	Sent AT Command: AT%XPTW=4,"0000"
701	378.509237			AT	16	Rcvd AT Command: OK  
702	378.509603			AT	32	Sent AT Command: AT+CEDRXS=2,5,"0000"
703	378.509634			AT	16	Rcvd AT Command: OK  
704	378.510031			AT	28	Sent AT Command: AT%XPTW=5,"0000"
705	378.510061			AT	16	Rcvd AT Command: OK  
706	378.510580			AT	20	Sent AT Command: AT%RAI=0
707	378.510611			AT	16	Rcvd AT Command: OK  
708	378.510977			AT	20	Sent AT Command: AT+CMEE?
709	378.511007			AT	26	Rcvd AT Command: +CMEE: 0  OK  
710	378.517569			AT	21	Sent AT Command: AT+CMEE=1
711	378.517599			AT	16	Rcvd AT Command: OK  
712	378.518026			AT	19	Sent AT Command: AT%CMNG
713	378.551748			AT	16	Rcvd AT Command: OK  
714	378.552114			AT	21	Sent AT Command: AT+CMEE=0
715	378.552145			AT	16	Rcvd AT Command: OK  
716	378.552542			AT	19	Sent AT Command: AT+CGSN
717	378.552603			AT	33	Rcvd AT Command: 351358816873084  OK  
718	378.553152			AT	24	Sent AT Command: AT%HWVERSION
719	378.553274			AT	46	Rcvd AT Command: %HWVERSION: nRF9160 SIAA B1A  OK  
720	378.564718			AT	20	Sent AT Command: AT+CMEE?
721	378.564749			AT	26	Rcvd AT Command: +CMEE: 0  OK  
722	378.565145			AT	21	Sent AT Command: AT+CMEE=1
723	378.565176			AT	16	Rcvd AT Command: OK  
724	378.565603			AT	19	Sent AT Command: AT%CMNG
725	378.594473			AT	16	Rcvd AT Command: OK  
726	378.594931			AT	21	Sent AT Command: AT+CMEE=0
727	378.594931			AT	16	Rcvd AT Command: OK  
728	378.595358			AT	20	Sent AT Command: AT+CMEE?
729	378.595388			AT	26	Rcvd AT Command: +CMEE: 0  OK  
730	378.601797			AT	21	Sent AT Command: AT+CMEE=1
731	378.601828			AT	16	Rcvd AT Command: OK  
732	378.602224			AT	19	Sent AT Command: AT%CMNG
733	378.630911			AT	16	Rcvd AT Command: OK  
734	378.631369			AT	21	Sent AT Command: AT+CMEE=0
735	378.631369			AT	16	Rcvd AT Command: OK  
736	378.631796			AT	20	Sent AT Command: AT+CMEE?
737	378.631826			AT	26	Rcvd AT Command: +CMEE: 0  OK  
738	378.638388			AT	21	Sent AT Command: AT+CMEE=1
739	378.638418			AT	16	Rcvd AT Command: OK  
740	378.638815			AT	19	Sent AT Command: AT%CMNG
741	378.667684			AT	16	Rcvd AT Command: OK  
742	378.668142			AT	21	Sent AT Command: AT+CMEE=0
743	378.668142			AT	16	Rcvd AT Command: OK  
744	378.677816			AT	20	Sent AT Command: AT+CMEE?
745	378.677816			AT	26	Rcvd AT Command: +CMEE: 0  OK  
746	378.678244			AT	21	Sent AT Command: AT+CMEE=1
747	378.678274			AT	16	Rcvd AT Command: OK  
748	378.678732			AT	19	Sent AT Command: AT%CMNG
749	378.707571			AT	16	Rcvd AT Command: OK  
750	378.814871			AT	21	Sent AT Command: AT+CEREG?
751	378.814962			AT	29	Rcvd AT Command: +CEREG: 0,4  OK  
752	378.821371			AT	20	Sent AT Command: AT+CFUN?
753	378.821432			AT	26	Rcvd AT Command: +CFUN: 0  OK  
754	378.821859			AT	22	Sent AT Command: AT+CEREG=5
755	378.821890			AT	16	Rcvd AT Command: OK  
756	378.822409			AT	36	Sent AT Command: AT%XT3412=1,5000,1200000
757	378.822439			AT	16	Rcvd AT Command: OK  
758	378.822866			AT	22	Sent AT Command: AT+CSCON=1
759	378.822866			AT	16	Rcvd AT Command: OK  
760	378.823263			AT	21	Sent AT Command: AT+CFUN=1
761	378.854574			AT	16	Rcvd AT Command: OK  
762	381.096304			LTE RRC DL_SCH	60	SystemInformationBlockType1
763	381.142416			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
764	381.146322			NAS-EPS	110	Attach request, PDN connectivity request
765	381.148092			AT	43	Rcvd AT Command: +CEREG: 2,"CEA5","0688000B",7  
766	381.148977			AT	22	Sent AT Command: AT%XTIME=1
767	381.149008			AT	16	Rcvd AT Command: OK  
768	381.262442			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
769	381.265249			LTE RRC UL_CCCH	30	RRCConnectionRequest
770	381.288534			LTE RRC DL_CCCH	71	RRCConnectionSetup
771	381.289541			LTE RRC UL_DCCH/NAS-EPS	129	RRCConnectionSetupComplete, Attach request, PDN connectivity request
772	381.290975			AT	23	Rcvd AT Command: +CSCON: 1  
773	381.612509			LTE RRC DL_DCCH/NAS-EPS	63	DLInformationTransfer, Authentication request
774	381.612570			NAS-EPS	52	Authentication request
775	381.646170			NAS-EPS	27	Authentication response
776	381.646475			LTE RRC UL_DCCH/NAS-EPS	44	ULInformationTransfer, Authentication response
777	381.740530			LTE RRC DL_DCCH/NAS-EPS	41	DLInformationTransfer, Security mode command
778	381.740591			NAS-EPS	30	Security mode command
779	381.741964			NAS-EPS	29	Security mode complete
780	381.742086			LTE RRC UL_DCCH/NAS-EPS	46	ULInformationTransfer, Ciphered message
781	382.935598			LTE RRC DL_DCCH	27	SecurityModeCommand
782	382.937033			LTE RRC UL_DCCH	26	SecurityModeComplete
783	382.998617			LTE RRC DL_DCCH	50	UECapabilityEnquiry
784	383.000418			LTE RRC UL_DCCH	136	UECapabilityInformation
785	383.120718			LTE RRC DL_DCCH/NAS-EPS	181	RRCConnectionReconfiguration, Ciphered message
786	383.121633			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
787	383.121847			NAS-EPS	143	Attach accept, Activate default EPS bearer context request (PDN type IPv4 only allowed)
788	383.122518			NAS-EPS	23	Attach complete, Activate default EPS bearer context accept
789	383.122671			LTE RRC UL_DCCH/NAS-EPS	40	ULInformationTransfer, Ciphered message
790	383.158651			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
791	383.158987			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
792	383.168417			AT	67	Rcvd AT Command: +CEREG: 5,"CEA5","0688000B",7,,,"11100000","11100000"  
793	383.169363			AT	21	Sent AT Command: AT%CESQ=1
794	383.169363			AT	16	Rcvd AT Command: OK  
795	383.169760			AT	21	Sent AT Command: AT+CEREG?
796	383.170004			AT	73	Rcvd AT Command: +CEREG: 5,5,"CEA5","0688000B",7,,,"11100000","11100000"  OK  
797	383.170584			AT	23	Sent AT Command: AT%XMONITOR
798	383.170797			AT	117	Rcvd AT Command: %XMONITOR: 5,"","","26003","CEA5",7,20,"0688000B",19,6200,65,33,"","11100000","11100000","01011110"  OK  
799	383.171591			AT	20	Sent AT Command: AT+CMEE?
800	383.171621			AT	26	Rcvd AT Command: +CMEE: 0  OK  
801	383.172293			AT	21	Sent AT Command: AT%XCBAND
802	383.172354			AT	29	Rcvd AT Command: %XCBAND: 20  OK  
803	383.172903			AT	21	Sent AT Command: AT+CMEE=1
804	383.172934			AT	16	Rcvd AT Command: OK  
805	383.173605			AT	23	Sent AT Command: AT%XCBAND=?
806	383.173696			AT	67	Rcvd AT Command: %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)  OK  
807	383.174490			AT	19	Sent AT Command: AT%CMNG
808	383.175589			LTE RRC DL_DCCH/NAS-EPS	64	DLInformationTransfer, Ciphered message
809	383.175711			NAS-EPS	53	EMM information
810	383.192617			LTE RRC DL_DCCH/NAS-EPS	64	DLInformationTransfer, Ciphered message
811	383.192739			NAS-EPS	53	EMM information
812	383.216207			AT	16	Rcvd AT Command: OK  
813	383.216604			AT	44	Rcvd AT Command: %XTIME: ,"42010101532380","01"  
814	383.216787			AT	44	Rcvd AT Command: %XTIME: ,"42010101533380","01"  
815	383.317007			AT	23	Sent AT Command: AT+CGDCONT?
816	383.317099			AT	30	Rcvd AT Command: %CESQ: 65,3,16,2  
817	383.317465			AT	69	Rcvd AT Command: +CGDCONT: 0,"IP","<HOST>","<LOCAL_IP>",0,0  OK  
818	383.318563			AT	21	Sent AT Command: AT+CMEE=0
819	383.318594			AT	16	Rcvd AT Command: OK  
820	383.318960			AT	22	Sent AT Command: AT+CEMODE?
821	383.318991			AT	28	Rcvd AT Command: +CEMODE: 2  OK  
822	383.319570			AT	20	Sent AT Command: AT+CMEE?
823	383.319570			AT	26	Rcvd AT Command: +CMEE: 0  OK  
824	383.319967			AT	20	Sent AT Command: AT+COPS?
825	383.320059			AT	38	Rcvd AT Command: +COPS: 0,2,"26003",7  OK  
826	383.320639			AT	21	Sent AT Command: AT+CMEE=1
827	383.320669			AT	16	Rcvd AT Command: OK  
828	383.321035			AT	21	Sent AT Command: AT+CEREG?
829	383.321188			AT	73	Rcvd AT Command: +CEREG: 5,5,"CEA5","0688000B",7,,,"11100000","11100000"  OK  
830	383.322164			AT	19	Sent AT Command: AT%CMNG
831	383.355062			AT	21	Rcvd AT Command: Sensitive
832	383.355520			AT	21	Sent AT Command: AT+CEREG?
833	383.355673			AT	73	Rcvd AT Command: +CEREG: 5,5,"CEA5","0688000B",7,,,"11100000","11100000"  OK  
834	383.356497			AT	21	Sent AT Command: AT+CMEE=0
835	383.356527			AT	16	Rcvd AT Command: OK  
836	383.357046			AT	27	Sent AT Command: AT%XSYSTEMMODE?
837	383.357077			AT	39	Rcvd AT Command: %XSYSTEMMODE: 1,0,0,0  OK  
838	383.357870			AT	27	Sent AT Command: AT%XSYSTEMMODE?
839	383.357901			AT	39	Rcvd AT Command: %XSYSTEMMODE: 1,0,0,0  OK  
840	383.358511	<LOCAL_IP>	8.8.8.8	DNS	73	Standard query 0x3d71 A <BOOTSTRAP_SERVER_HOST>
841	383.359335			AT	27	Sent AT Command: AT%XSYSTEMMODE?
842	383.359365			AT	39	Rcvd AT Command: %XSYSTEMMODE: 1,0,0,0  OK  
843	383.359945			AT	20	Sent AT Command: AT+CMEE?
844	383.359976			AT	26	Rcvd AT Command: +CMEE: 0  OK  
845	383.360403			AT	23	Sent AT Command: AT+CGDCONT?
846	383.360525			AT	69	Rcvd AT Command: +CGDCONT: 0,"IP","<HOST>","<LOCAL_IP>",0,0  OK  
847	383.361380			AT	21	Sent AT Command: AT+CMEE=1
848	383.361410			AT	16	Rcvd AT Command: OK  
849	383.361898			AT	19	Sent AT Command: AT+CESQ
850	383.361929			AT	44	Rcvd AT Command: +CESQ: 99,99,255,255,16,65  OK  
851	383.362631			AT	19	Sent AT Command: AT%CMNG
852	383.397665			AT	16	Rcvd AT Command: OK  
853	383.398153			AT	36	Sent AT Command: AT+CRSM=176,12258,0,0,10
854	383.416769			AT	53	Rcvd AT Command: +CRSM: 144,0,"98882208660645235687"  OK  
855	383.417562			AT	21	Sent AT Command: AT+CMEE=0
856	383.417593			AT	16	Rcvd AT Command: OK  
857	383.418020			AT	19	Sent AT Command: AT+CIMI
858	383.418020			AT	33	Rcvd AT Command: 901405105432657  OK  
859	383.418600			AT	20	Sent AT Command: AT+CMEE?
860	383.418600			AT	26	Rcvd AT Command: +CMEE: 0  OK  
861	383.419058			AT	19	Sent AT Command: AT+CGMR
862	383.419088			AT	35	Rcvd AT Command: mfw_nrf9160_1.3.6  OK  
863	383.419638			AT	21	Sent AT Command: AT+CMEE=1
864	383.419668			AT	16	Rcvd AT Command: OK  
865	383.420156			AT	20	Sent AT Command: AT%XVBAT
866	383.420187			AT	30	Rcvd AT Command: %XVBAT: 3825  OK  
867	383.420980			AT	19	Sent AT Command: AT%CMNG
868	383.449758	8.8.8.8	<LOCAL_IP>	DNS	89	Standard query response 0x3d71 A <BOOTSTRAP_SERVER_HOST> A <BOOTSTRAP_SERVER_IP>
869	383.453146	<LOCAL_IP>	<BOOTSTRAP_SERVER_IP>	CoAP	89	CON, MID:56360, POST, TKN:55 dc 69 a5 a0 40 46 3e, /bs?ep=<MY_ENDPOINT>&pct=112
870	383.463888			AT	21	Rcvd AT Command: Sensitive
871	383.464559			AT	19	Sent AT Command: AT+CGSN
872	383.464651			AT	33	Rcvd AT Command: 351358816873084  OK  
873	383.465811			AT	21	Sent AT Command: AT+CMEE=0
874	383.465841			AT	16	Rcvd AT Command: OK  
875	383.541616	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	52	ACK, MID:56360, 2.04 Changed, TKN:55 dc 69 a5 a0 40 46 3e, /bs
876	383.541677	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	54	CON, MID:43820, DELETE, TKN:20 5d 90 aa f3 4b c0 f8, /0
877	383.550833	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43820, 2.02 Deleted, TKN:20 5d 90 aa f3 4b c0 f8, /0
878	383.708517	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	54	CON, MID:43821, DELETE, TKN:bc da d7 f6 d6 2f 04 d7, /1
879	383.712789	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43821, 2.02 Deleted, TKN:bc da d7 f6 d6 2f 04 d7, /1
880	383.786611	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	169	CON, MID:43822, PUT, TKN:b4 05 1e aa b6 b8 2f a7, /0/0
881	383.790579	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43822, 2.04 Changed, TKN:b4 05 1e aa b6 b8 2f a7, /0/0
882	383.866659	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	219	CON, MID:43823, PUT, TKN:8c 6b 9a cd 24 c9 f2 21, /0/1
883	383.880941	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43823, 2.04 Changed, TKN:8c 6b 9a cd 24 c9 f2 21, /0/1
884	383.994650	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	101	CON, MID:43824, PUT, TKN:f8 e9 85 df d5 f2 64 1e, /1/0
885	384.002157	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43824, 2.04 Changed, TKN:f8 e9 85 df d5 f2 64 1e, /1/0
886	384.103567	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43825, PUT, TKN:70 f3 84 07 02 32 ca 18, /10351/0
887	384.106161	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43825, 4.04 Not Found, TKN:70 f3 84 07 02 32 ca 18, /10351/0
888	384.259573	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43826, PUT, TKN:f4 cb 52 80 e1 5b 6a 12, /10351/1
889	384.262136	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43826, 4.04 Not Found, TKN:f4 cb 52 80 e1 5b 6a 12, /10351/1
890	384.417562	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43827, PUT, TKN:cc a6 56 2f f3 cf 13 7c, /10351/2
891	384.420187	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43827, 4.04 Not Found, TKN:cc a6 56 2f f3 cf 13 7c, /10351/2
892	384.525625	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43828, PUT, TKN:ec ca e4 7f 2d fc b8 97, /10351/3
893	384.528219	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43828, 4.04 Not Found, TKN:ec ca e4 7f 2d fc b8 97, /10351/3
894	384.659597	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43829, PUT, TKN:20 b0 ab 40 29 ff 17 51, /10351/4
895	384.662161	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43829, 4.04 Not Found, TKN:20 b0 ab 40 29 ff 17 51, /10351/4
896	384.817587	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43830, PUT, TKN:5c e7 5f da 96 6b 1d 22, /10351/5
897	384.820211	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43830, 4.04 Not Found, TKN:5c e7 5f da 96 6b 1d 22, /10351/5
898	384.970602	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43831, PUT, TKN:b0 f3 8c ad 28 54 82 e0, /10351/6
899	384.973165	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43831, 4.04 Not Found, TKN:b0 f3 8c ad 28 54 82 e0, /10351/6
900	385.057608	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43832, PUT, TKN:dc 63 68 88 6a af 2c bf, /10351/7
901	385.060202	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43832, 4.04 Not Found, TKN:dc 63 68 88 6a af 2c bf, /10351/7
902	385.216635	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43833, PUT, TKN:c0 ca 16 9c 80 33 92 07, /10351/8
903	385.219198	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43833, 4.04 Not Found, TKN:c0 ca 16 9c 80 33 92 07, /10351/8
904	385.379660	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	89	CON, MID:43834, PUT, TKN:e8 9d 24 38 f4 e4 30 ef, /10351/9
905	385.382254	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43834, 4.04 Not Found, TKN:e8 9d 24 38 f4 e4 30 ef, /10351/9
906	385.495596	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43835, PUT, TKN:60 f7 e6 58 85 24 86 a6, /10351/10
907	385.498220	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43835, 4.04 Not Found, TKN:60 f7 e6 58 85 24 86 a6, /10351/10
908	385.617605	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43836, PUT, TKN:78 8b 53 5a ae 5f 6f ae, /10351/11
909	385.620230	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43836, 4.04 Not Found, TKN:78 8b 53 5a ae 5f 6f ae, /10351/11
910	385.776632	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43837, PUT, TKN:88 9a d4 f3 9c cf 92 3b, /10351/12
911	385.779226	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43837, 4.04 Not Found, TKN:88 9a d4 f3 9c cf 92 3b, /10351/12
912	385.935629	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43838, PUT, TKN:18 95 90 a7 7b 38 30 7c, /10351/13
913	385.938223	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43838, 4.04 Not Found, TKN:18 95 90 a7 7b 38 30 7c, /10351/13
914	386.020620	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43839, PUT, TKN:d0 ae 32 0a 24 1d ac 11, /10351/14
915	386.023184	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43839, 4.04 Not Found, TKN:d0 ae 32 0a 24 1d ac 11, /10351/14
916	386.176687	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43840, PUT, TKN:88 a7 09 a4 05 dd a8 9e, /10351/15
917	386.179312	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43840, 4.04 Not Found, TKN:88 a7 09 a4 05 dd a8 9e, /10351/15
918	386.346640	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43841, PUT, TKN:38 c5 7d e2 ab a6 c0 ca, /10351/16
919	386.349264	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43841, 4.04 Not Found, TKN:38 c5 7d e2 ab a6 c0 ca, /10351/16
920	386.475698	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43842, PUT, TKN:24 9e 6a ac 63 8f fc ac, /10351/17
921	386.478292	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43842, 4.04 Not Found, TKN:24 9e 6a ac 63 8f fc ac, /10351/17
922	386.576681	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43843, PUT, TKN:e0 19 e4 74 92 d5 04 7f, /10351/18
923	386.579275	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43843, 4.04 Not Found, TKN:e0 19 e4 74 92 d5 04 7f, /10351/18
924	386.652670	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43844, PUT, TKN:04 46 e9 d7 8f 69 40 8f, /10351/19
925	386.655264	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43844, 4.04 Not Found, TKN:04 46 e9 d7 8f 69 40 8f, /10351/19
926	386.729666	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43845, PUT, TKN:b0 0b b1 b8 77 bf 98 e9, /10351/20
927	386.732260	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43845, 4.04 Not Found, TKN:b0 0b b1 b8 77 bf 98 e9, /10351/20
928	386.817678	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43846, PUT, TKN:28 37 b3 85 d7 d4 d3 f9, /10351/21
929	386.820242	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43846, 4.04 Not Found, TKN:28 37 b3 85 d7 d4 d3 f9, /10351/21
930	386.981649	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43847, PUT, TKN:58 56 b4 1e f5 4e b1 d3, /10351/22
931	386.984274	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43847, 4.04 Not Found, TKN:58 56 b4 1e f5 4e b1 d3, /10351/22
932	387.137655	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43848, PUT, TKN:3c 6c a1 93 5b 1e 84 1a, /10351/23
933	387.140249	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43848, 4.04 Not Found, TKN:3c 6c a1 93 5b 1e 84 1a, /10351/23
934	387.297720	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43849, PUT, TKN:94 e8 2b 46 3c 61 d9 61, /10351/24
935	387.300283	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43849, 4.04 Not Found, TKN:94 e8 2b 46 3c 61 d9 61, /10351/24
936	387.457693	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43850, PUT, TKN:28 3e 26 be 8c 7b 44 a9, /10351/25
937	387.460348	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43850, 4.04 Not Found, TKN:28 3e 26 be 8c 7b 44 a9, /10351/25
938	387.626699	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43851, PUT, TKN:d4 6d b9 11 9b 78 17 08, /10351/26
939	387.629293	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43851, 4.04 Not Found, TKN:d4 6d b9 11 9b 78 17 08, /10351/26
940	387.776724	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43852, PUT, TKN:b0 22 7a 7f b9 3e 84 75, /10351/27
941	387.779318	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43852, 4.04 Not Found, TKN:b0 22 7a 7f b9 3e 84 75, /10351/27
942	387.936697	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43853, PUT, TKN:dc 98 51 c5 97 25 ee 7b, /10351/28
943	387.939291	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43853, 4.04 Not Found, TKN:dc 98 51 c5 97 25 ee 7b, /10351/28
944	388.026693	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43854, PUT, TKN:14 18 3d de a3 a7 1d 76, /10351/29
945	388.029257	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43854, 4.04 Not Found, TKN:14 18 3d de a3 a7 1d 76, /10351/29
946	388.179739	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43855, PUT, TKN:60 f5 94 ab 97 f5 dc 8f, /10351/30
947	388.182333	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43855, 4.04 Not Found, TKN:60 f5 94 ab 97 f5 dc 8f, /10351/30
948	388.337698	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	91	CON, MID:43856, PUT, TKN:30 74 79 83 a9 04 ac 36, /10351/31
949	388.340292	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43856, 4.04 Not Found, TKN:30 74 79 83 a9 04 ac 36, /10351/31
950	388.485647	<LESHAN_SERVER_IP>	<LOCAL_IP>	CoAP	55	CON, MID:43857, POST, TKN:ac 2a ab 5d e2 d9 d0 dd, /bs
951	388.486776	<LOCAL_IP>	<LESHAN_SERVER_IP>	CoAP	52	ACK, MID:43857, 2.04 Changed, TKN:ac 2a ab 5d e2 d9 d0 dd, /bs
952	389.489340	<LOCAL_IP>	8.8.8.8	DNS	77	Standard query 0x7c71 A <LESHAN_SERVER_HOST>
953	389.619802	8.8.8.8	<LOCAL_IP>	DNS	93	Standard query response 0x7c71 A <LESHAN_SERVER_HOST> A <LESHAN_SERVER_IP>
954	389.620718			AT	20	Sent AT Command: AT+CMEE?
955	389.620718			AT	26	Rcvd AT Command: +CMEE: 0  OK  
956	389.621145			AT	21	Sent AT Command: AT+CMEE=1
957	389.621145			AT	16	Rcvd AT Command: OK  
958	389.621603			AT	19	Sent AT Command: AT%CMNG
959	389.661673			AT	16	Rcvd AT Command: OK  
960	389.662069			AT	21	Sent AT Command: AT+CMEE=0
961	389.662100			AT	16	Rcvd AT Command: OK  
962	389.662680			AT	20	Sent AT Command: AT+CMEE?
963	389.662680			AT	26	Rcvd AT Command: +CMEE: 0  OK  
964	389.663107			AT	21	Sent AT Command: AT+CMEE=1
965	389.663107			AT	16	Rcvd AT Command: OK  
966	389.663717			AT	19	Sent AT Command: AT%CMNG
967	389.704580			AT	21	Rcvd AT Command: Sensitive
968	389.705038			AT	21	Sent AT Command: AT+CMEE=0
969	389.705038			AT	16	Rcvd AT Command: OK  
970	389.705648			AT	20	Sent AT Command: AT+CFUN?
971	389.705740			AT	26	Rcvd AT Command: +CFUN: 1  OK  
972	389.706198			AT	21	Sent AT Command: AT+CFUN=4
973	389.707205			NAS-EPS	31	Detach request (Combined EPS/IMSI detach / switch-off)
974	389.707327			LTE RRC UL_DCCH/NAS-EPS	48	ULInformationTransfer, Ciphered message
975	389.799063			AT	23	Rcvd AT Command: +CEREG: 0  
976	389.896780			LTE RRC DL_DCCH	26	RRCConnectionRelease [cause=other]
977	390.895803			AT	30	Rcvd AT Command: %CESQ: 62,3,11,1  
978	391.159750			AT	32	Rcvd AT Command: %CESQ: 255,0,255,0  
979	391.161428			AT	23	Rcvd AT Command: +CSCON: 0  
980	391.229055			AT	16	Rcvd AT Command: OK  
981	391.229513			AT	20	Sent AT Command: AT+CMEE?
982	391.229513			AT	26	Rcvd AT Command: +CMEE: 0  OK  
983	391.229971			AT	21	Sent AT Command: AT+CMEE=1
984	391.229971			AT	16	Rcvd AT Command: OK  
985	391.230429			AT	19	Sent AT Command: AT%CMNG
986	391.265005			AT	16	Rcvd AT Command: OK  
987	391.265463			AT	21	Sent AT Command: AT+CMEE=0
988	391.265463			AT	16	Rcvd AT Command: OK  
989	391.265921			AT	20	Sent AT Command: AT+CMEE?
990	391.265921			AT	26	Rcvd AT Command: +CMEE: 0  OK  
991	391.266348			AT	21	Sent AT Command: AT+CMEE=1
992	391.266378			AT	16	Rcvd AT Command: OK  
993	391.267019			AT	19	Sent AT Command: AT%CMNG
994	391.319479			AT	16	Rcvd AT Command: OK  
995	391.319906			AT	21	Sent AT Command: AT+CMEE=0
996	391.319906			AT	16	Rcvd AT Command: OK  
997	391.320333			AT	20	Sent AT Command: AT+CFUN?
998	391.320394			AT	26	Rcvd AT Command: +CFUN: 4  OK  
999	391.320822			AT	21	Sent AT Command: AT+CEREG?
1000	391.320913			AT	29	Rcvd AT Command: +CEREG: 5,0  OK  
1001	391.327352			AT	20	Sent AT Command: AT+CFUN?
1002	391.327413			AT	26	Rcvd AT Command: +CFUN: 4  OK  
1003	391.327810			AT	22	Sent AT Command: AT+CEREG=5
1004	391.327810			AT	16	Rcvd AT Command: OK  
1005	391.328360			AT	36	Sent AT Command: AT%XT3412=1,5000,1200000
1006	391.328390			AT	16	Rcvd AT Command: OK  
1007	391.328756			AT	22	Sent AT Command: AT+CSCON=1
1008	391.328787			AT	16	Rcvd AT Command: OK  
1009	391.329153			AT	21	Sent AT Command: AT+CFUN=1
1010	391.360098			AT	16	Rcvd AT Command: OK  
1011	392.216604			LTE RRC DL_SCH	60	SystemInformationBlockType1
1012	392.217153			LTE RRC DL_SCH	117	SystemInformation [ SIB2 SIB3 ]
1013	392.217337			LTE RRC DL_SCH	117	SystemInformation [ SIB5 ]
1014	392.219625			NAS-EPS	110	Attach request, PDN connectivity request
1015	392.221395			AT	29	Rcvd AT Command: %CESQ: 57,2,4,0  
1016	392.221548			AT	43	Rcvd AT Command: +CEREG: 2,"CEA5","0688000B",7  
1017	392.222525			AT	22	Sent AT Command: AT%XTIME=1
1018	392.222555			AT	16	Rcvd AT Command: OK  
1019	392.227560			LTE RRC UL_CCCH	30	RRCConnectionRequest
1020	392.268820			LTE RRC DL_CCCH	71	RRCConnectionSetup
1021	392.269796			LTE RRC UL_DCCH/NAS-EPS	129	RRCConnectionSetupComplete, Attach request, PDN connectivity request
1022	392.271261			AT	23	Rcvd AT Command: +CSCON: 1  
1023	392.281790			AT	30	Rcvd AT Command: %CESQ: 59,2,10,1  
1024	392.516806			LTE RRC DL_DCCH/NAS-EPS	36	DLInformationTransfer
1025	392.516958			IP	21	Bogus IP version (2)
1026	392.516989			IP	24	Bogus IP version (0)
1027	392.517141			LTE RRC UL_DCCH/NAS-EPS	45	ULInformationTransfer, Ciphered message
1028	393.284811			AT	30	Rcvd AT Command: %CESQ: 59,2,15,2  
1029	393.624899			LTE RRC DL_DCCH	27	SecurityModeCommand
1030	393.626364			LTE RRC UL_DCCH	26	SecurityModeComplete
1031	393.717886			LTE RRC DL_DCCH	50	UECapabilityEnquiry
1032	393.719778			LTE RRC UL_DCCH	136	UECapabilityInformation
1033	393.833059			LTE RRC DL_DCCH/NAS-EPS	168	RRCConnectionReconfiguration, Ciphered message
1034	393.833853			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
1035	393.834066			NAS-EPS	130	Attach accept, Activate default EPS bearer context request (PDN type IPv4 only allowed)
1036	393.834677			NAS-EPS	23	Attach complete, Activate default EPS bearer context accept
1037	393.834799			LTE RRC UL_DCCH/NAS-EPS	40	ULInformationTransfer, Ciphered message
1038	393.876944			LTE RRC DL_DCCH	47	RRCConnectionReconfiguration
1039	393.877249			LTE RRC UL_DCCH	26	RRCConnectionReconfigurationComplete
1040	393.886862			AT	67	Rcvd AT Command: +CEREG: 5,"CEA5","0688000B",7,,,"11100000","11100000"  
1041	393.888021			AT	21	Sent AT Command: AT%CESQ=1
1042	393.888021			AT	16	Rcvd AT Command: OK  
1043	393.888693			AT	23	Sent AT Command: AT%XMONITOR
1044	393.891104			AT	129	Rcvd AT Command: %XMONITOR: 5,"Orange","Orange","26003","CEA5",7,20,"0688000B",19,6200,60,27,"","11100000","11100000","01011110"  OK  
1045	393.893881			LTE RRC DL_DCCH/NAS-EPS	64	DLInformationTransfer, Ciphered message
1046	393.894003			NAS-EPS	53	EMM information
1047	393.894339			AT	21	Sent AT Command: AT%XCBAND
1048	393.894491			AT	44	Rcvd AT Command: %XTIME: ,"42010101533480","01"  
1049	393.894827			AT	29	Rcvd AT Command: %XCBAND: 20  OK  
1050	393.912863			LTE RRC DL_DCCH/NAS-EPS	64	DLInformationTransfer, Ciphered message
1051	393.912985			NAS-EPS	53	EMM information
1052	393.995047			AT	44	Rcvd AT Command: %XTIME: ,"42010101533480","01"  
1053	393.995779			AT	23	Sent AT Command: AT%XCBAND=?
1054	393.995871			AT	67	Rcvd AT Command: %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)  OK  
1055	393.996359			AT	23	Sent AT Command: AT+CGDCONT?
1056	393.996481			AT	69	Rcvd AT Command: +CGDCONT: 0,"IP","iot.1nce.net","<LOCAL_IP>",0,0  OK  
1057	393.997824			AT	22	Sent AT Command: AT+CEMODE?
1058	393.997854			AT	28	Rcvd AT Command: +CEMODE: 2  OK  
1059	393.998403			AT	20	Sent AT Command: AT+COPS?
1060	393.998495			AT	38	Rcvd AT Command: +COPS: 0,2,"26003",7  OK  
1061	393.999319			AT	21	Sent AT Command: AT+CEREG?
1062	393.999441			AT	73	Rcvd AT Command: +CEREG: 5,5,"CEA5","0688000B",7,,,"11100000","11100000"  OK  
1063	394.000448			AT	21	Sent AT Command: AT+CEREG?
1064	394.000845			AT	73	Rcvd AT Command: +CEREG: 5,5,"CEA5","0688000B",7,,,"11100000","11100000"  OK  
1065	394.001944			AT	27	Sent AT Command: AT%XSYSTEMMODE?
1066	394.001974			AT	39	Rcvd AT Command: %XSYSTEMMODE: 1,0,0,0  OK  
1067	394.002951			AT	27	Sent AT Command: AT%XSYSTEMMODE?
1068	394.002981			AT	39	Rcvd AT Command: %XSYSTEMMODE: 1,0,0,0  OK  
1069	394.003866			AT	27	Sent AT Command: AT%XSYSTEMMODE?
1070	394.003897			AT	39	Rcvd AT Command: %XSYSTEMMODE: 1,0,0,0  OK  
1071	394.004721			AT	23	Sent AT Command: AT+CGDCONT?
1072	394.004843			AT	69	Rcvd AT Command: +CGDCONT: 0,"IP","iot.1nce.net","<LOCAL_IP>",0,0  OK  
1073	394.005758			AT	19	Sent AT Command: AT+CESQ
1074	394.005789			AT	44	Rcvd AT Command: +CESQ: 99,99,255,255,14,60  OK  
1075	394.006765			AT	36	Sent AT Command: AT+CRSM=176,12258,0,0,10
1076	394.025167			AT	53	Rcvd AT Command: +CRSM: 144,0,"98882208660645235687"  OK  
1077	394.025869			AT	19	Sent AT Command: AT+CIMI
1078	394.025869			AT	33	Rcvd AT Command: 901405105432657  OK  
1079	394.026449			AT	19	Sent AT Command: AT+CGMR
1080	394.026480			AT	35	Rcvd AT Command: mfw_nrf9160_1.3.6  OK  
1081	394.027304			AT	20	Sent AT Command: AT%XVBAT
1082	394.027334			AT	30	Rcvd AT Command: %XVBAT: 3825  OK  
1083	394.027883			AT	19	Sent AT Command: AT+CGSN
1084	394.027975			AT	33	Rcvd AT Command: 351358816873084  OK  
1085	394.892721	<LOCAL_IP>	<LESHAN_SERVER_IP>	DTLS	138	Client Hello
1086	396.893545	<LOCAL_IP>	<LESHAN_SERVER_IP>	DTLS	138	Client Hello
1087	400.894186	<LOCAL_IP>	<LESHAN_SERVER_IP>	DTLS	138	Client Hello

RE: Help with LTE connection after loss of connection

SeppoTakalo — Wed, 09 Oct 2024 10:02:01 GMT

[quote userid="133668" url="~/f/nordic-q-a/114133/help-with-lte-connection-after-loss-of-connection/505376"]

We set the value to 5s, and the board starts to reregister after 5s instead of after 247s.

This is exactly how we want the board to behave. Is there any other way to declare the exchange timeouts?

[/quote]

Have you checked with Wireshark what is exactly happening if you do this?

What problem do you expect this to fix?

I tried to explain in RE: Help with LTE connection after loss of connection why it does not make sense to modify CoAP timeouts for just one specific messages.

It is highly likely that you need, or want, to modify CoAP timeouts to match the network, but do it globally for all messages. Equally consider what happens in DTLS layer and IP+network layer. When you see problems in application layer protocol (LwM2M) you most probably need to fix the problem on the layer below.

RE: Help with LTE connection after loss of connection

dejans — Wed, 09 Oct 2024 09:27:47 GMT

Hi,

You can create an issue and provide PR for resolving it. You could also provide a link to your PR in this ticket.

Best regards,
Dejan

RE: Help with LTE connection after loss of connection

Matias Marti — Tue, 08 Oct 2024 13:48:50 GMT

[quote userid="111786" url="~/f/nordic-q-a/114133/help-with-lte-connection-after-loss-of-connection/499589"]Have you tried changing the value directly in the code?
[/quote]

dejans SeppoTakalo

We have now tried changing the value directly in the sdk, and this is how the logs look now:

[00:01:03.867,492] <inf> app_lwm2m_client: LwM2M is connected to server
[00:01:03.867,584] <inf> app_lwm2m_client: Obtained date-time from modem
[00:01:22.783,782] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:01:27.884,124] <dbg> app_lwm2m_client: rd_client_event: Registration update failure!
[00:01:27.891,876] <inf> net_lwm2m_rd_client: RD Client started with endpoint '<MY_ENDPOINT>' with client lifetime 86400 using server object 0
[00:01:29.245,269] <inf> net_lwm2m_engine: Connected, sock id 2
[00:01:29.248,382] <dbg> app_lwm2m_client: rd_client_event: Disconnected
[00:01:29.248,504] <inf> net_lwm2m_rd_client: Stop LWM2M Client: <MY_ENDPOINT>
[00:01:29.334,838] <inf> app_lwm2m_client: Client connect to server
[00:01:29.334,869] <inf> net_lwm2m_rd_client: Start LWM2M Client: <MY_ENDPOINT>
[00:01:29.335,540] <inf> net_lwm2m_rd_client: RD Client started with endpoint '<MY_ENDPOINT>' with client lifetime 86400 using server object 0
[00:01:29.460,998] <inf> app_lwm2m_client: LwM2M is connecting to server
[00:01:29.632,720] <inf> net_lwm2m_engine: Connected, sock id 2
[00:01:29.785,278] <dbg> app_lwm2m_client: rd_client_event: Registration complete
[00:01:29.785,430] <inf> net_lwm2m_rd_client: Registration Done (EP='xxxx')
[00:01:29.868,164] <inf> app_lwm2m_client: LwM2M is connected to server
[00:01:29.868,225] <inf> app_lwm2m_client: Obtained date-time from modem
[00:01:48.784,393] <dbg> app_lwm2m_client: rd_client_event: Registration update started
[00:01:53.886,108] <dbg> app_lwm2m_client: rd_client_event: Registration update failure!
[00:01:53.893,859] <inf> net_lwm2m_rd_client: RD Client started with endpoint '<MY_ENDPOINT>' with client lifetime 86400 using server object 0
[00:01:55.007,781] <inf> net_lwm2m_engine: Connected, sock id 2
[00:01:55.010,894] <dbg> app_lwm2m_client: rd_client_event: Disconnected
[00:01:55.011,016] <inf> net_lwm2m_rd_client: Stop LWM2M Client: <MY_ENDPOINT>
[00:01:55.097,839] <inf> app_lwm2m_client: Client connect to server
[00:01:55.097,900] <inf> net_lwm2m_rd_client: Start LWM2M Client: <MY_ENDPOINT>
[00:01:55.098,541] <inf> net_lwm2m_rd_client: RD Client started with endpoint '<MY_ENDPOINT>' with client lifetime 86400 using server object 0
[00:01:55.223,052] <inf> app_lwm2m_client: LwM2M is connecting to server
[00:01:55.398,132] <inf> net_lwm2m_engine: Connected, sock id 2
[00:01:55.553,161] <dbg> app_lwm2m_client: rd_client_event: Registration complete
[00:01:55.553,314] <inf> net_lwm2m_rd_client: Registration Done (EP='xxxx')

We forced this error by making our Leshan server unresponsive. With the usual code, the failure log shows up 4min7s after the registration update starts. Now, by changing the exchange timeout for this specific message, the code behaves as we want to:

case ENGINE_UPDATE_SENT:
	/* wait update to be done or abort */
	timeout = EXCHANGE_LIFETIME;
	break;

We set the value to 5s, and the board starts to reregister after 5s instead of after 247s.

This is exactly how we want the board to behave. Is there any other way to declare the exchange timeouts? We do not want to fork the whole Github repo and make our customizations.

Should we create an issue and/or PR on Github for the sdk?

Again, thank you for you help.

RE: Help with LTE connection after loss of connection

lobaro-theo — Thu, 12 Sep 2024 07:19:53 GMT

I opened a new private ticket. But before I discovered that there is no dependency for this problem to the nrf_modem. It does not matter.

RE: Help with LTE connection after loss of connection

Matias Marti — Tue, 10 Sep 2024 09:57:37 GMT

Thank you @seppo . Here are some more interesing logs:

[1;32muart:~$ [m[8D[J[00:49:29.217,254] [0m<dbg> app_lwm2m_client: rd_client_event: Registration update complete[0m
[1;32muart:~$ [m[8D[J[00:49:29.217,285] [0m<dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok![0m
[1;32muart:~$ [m[8D[J[00:49:29.217,376] [0m<inf> net_lwm2m_rd_client: Update Done[0m
[1;32muart:~$ [m[8D[J[00:49:29.217,559] [0m<dbg> net_lwm2m_message_handling: lwm2m_udp_receive: reply 0x2000d7c0 handled and removed[0m
[1;32muart:~$ [m[8D[J[00:49:29.217,620] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 9[0m
[1;32muart:~$ [m[8D[J[00:49:29.252,838] [0m<dbg> at_monitor: at_monitor_task: AT notif: %CESQ: 39,1,17,2[0m
[1;32muart:~$ [m[8D[J[00:49:29.252,899] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3bef9[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:49:34.666,595] [0m<dbg> at_monitor: at_monitor_task: AT notif: +CSCON: 0[0m
[1;32muart:~$ [m[8D[J[00:49:34.666,625] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x39a7d[0m
[1;32muart:~$ [m[8D[J[00:49:34.666,656] [0m<dbg> lte_lc: at_handler_cscon: +CSCON notification[0m
[1;32muart:~$ [m[8D[J[00:49:34.666,809] [0m<dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=3[0m
[1;32muart:~$ [m[8D[J[00:49:34.666,839] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0003C989[0m
[1;32muart:~$ [m[8D[J[00:49:34.666,839] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00040D25[0m
[1;32muart:~$ [m[8D[J[00:49:34.666,870] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A8A5[0m
[1;32muart:~$ [m[8D[J[00:49:34.666,900] [0m<dbg> lte_lc: event_handler_list_dispatch: Done[0m
[1;32muart:~$ [m[8D[J[00:49:34.766,723] [0m<dbg> at_monitor: at_monitor_task: AT notif: %XT3412: 3239999[0m
[1;32muart:~$ [m[8D[J[00:49:34.766,754] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3992d[0m
[1;32muart:~$ [m[8D[J[00:49:34.766,815] [0m<dbg> lte_lc: at_handler_xt3412: %XT3412 notification[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:49:35.249,389] [0m<dbg> at_monitor: at_monitor_task: AT notif: %CESQ: 37,1,12,1[0m
[1;32muart:~$ [m[8D[J[00:49:35.249,450] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3bef9[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m*** Booting nRF Connect SDK v3.5.99-ncs1 ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x1
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0x10000
I: Jumping to the first image slot
�[m

[1;32muart:~$ [m[8D[J[00:00:00.252,258] [0m<dbg> clock_control: clkstarted_handle: lfclk: Clock started[0m
[1;32muart:~$ [m[8D[J*** Booting nRF Connect SDK v3.5.99-ncs1 ***
[1;32muart:~$ [m[8D[J[00:00:00.253,814] [0m<dbg> net_lwm2m_obj_qlocx_manage: management_create: Create IPSO Management instance: 0[0m
[1;32muart:~$ [m[8D[J[00:00:00.253,845] [0m<dbg> net_lwm2m_obj_qlocx_barcode: barcode_create: Create IPSO Barcode instance: 0[0m
[1;32muart:~$ [m[8D[J[00:00:00.254,577] [0m<dbg> net_lwm2m_engine: lwm2m_engine_init: LWM2M engine socket receive thread started[0m
[1;32muart:~$ [m[8D[J[00:00:00.254,699] [0m<dbg> net_lwm2m_obj_security: security_create: Create LWM2M security instance: 0[0m
[1;32muart:~$ [m[8D[J[00:00:00.254,821] [0m<dbg> net_lwm2m_obj_device: device_create: Create LWM2M device instance: 0[0m
[1;32muart:~$ [m[8D[J[00:00:00.255,187] [0m<dbg> net_lwm2m_obj_conn_mon: connmon_create: Create LWM2M connectivity monitoring instance: 0[0m
[1;32muart:~$ [m[8D[J[00:00:00.255,249] [0m<dbg> net_lwm2m_obj_firmware: firmware_create: Create LWM2M firmware instance: 0[0m
[1;32muart:~$ [m[8D[J[00:00:00.255,798] [0m<inf> app_lwm2m_client: Run LWM2M client[0m
[1;32muart:~$ [m[8D[J[00:00:00.255,828] [0m<dbg> app_lwm2m_client: watchdog_Init: Watchdog started: 0[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:00:00.487,518] [0m<dbg> nrf_modem: nrf_modem_lib_init: Modem init callback: 0x3bdf9[0m
[1;32muart:~$ [m[8D[J[00:00:00.495,758] [0m<dbg> lte_lc: lte_lc_system_mode_set: System mode set to 1, preference 0[0m
[1;32muart:~$ [m[8D[J[00:00:00.495,819] [0m<dbg> lte_lc: lte_lc_psm_param_set: RPTAU set to 00000110[0m
[1;32muart:~$ [m[8D[J[00:00:00.495,849] [0m<dbg> lte_lc: lte_lc_psm_param_set: RAT set to 00001111[0m
[1;32muart:~$ [m[8D[J[00:00:00.495,910] [0m<dbg> lte_lc: on_modem_init: PSM configs set from string: tau=00000110, rat=00001111[0m
[1;32muart:~$ [m[8D[J[00:00:00.495,971] [0m<dbg> lte_lc: lte_lc_psm_req: enable=0, tau=00000110, rat=00001111[0m
[1;32muart:~$ [m[8D[J[00:00:00.503,906] [0m<inf> app_lwm2m_client: Clearing PSK[0m
[1;32muart:~$ [m[8D[J[00:00:00.533,843] [0m<dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok![0m
[1;32muart:~$ [m[8D[J[00:00:00.533,905] [0m<dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok![0m
[1;32muart:~$ [m[8D[J[00:00:00.534,606] [0m<inf> app_lwm2m_client: endpoint: <MY_ENDPOINT>[0m
[1;32muart:~$ [m[8D[J[00:00:00.534,637] [0m<dbg> app_lwm2m_client: watchdog_Kick: Watchdog feed ok![0m

We have noticed that the device keeps restarting every 49.5 minutes... Is there any value in prj.conf that might be causing this?

Another point:

It seems like disabling PSM mode prevents the device from disconnecting:

[1;32muart:~$ [m[8D[J[00:25:43.377,349] [0m<dbg> net_lwm2m_message_handling: lwm2m_parse_peerinfo: Parse url: coaps://<MY_URL>:5684[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:25:47.265,747] [0m<dbg> at_monitor: at_monitor_task: AT notif: +CSCON: 0[0m
[1;32muart:~$ [m[8D[J[00:25:47.265,808] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x39a7d[0m
[1;32muart:~$ [m[8D[J[00:25:47.265,808] [0m<dbg> lte_lc: at_handler_cscon: +CSCON notification[0m
[1;32muart:~$ [m[8D[J[00:25:47.265,960] [0m<dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=3[0m
[1;32muart:~$ [m[8D[J[00:25:47.265,991] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0003C989[0m
[1;32muart:~$ [m[8D[J[00:25:47.266,021] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00040D25[0m
[1;32muart:~$ [m[8D[J[00:25:47.266,021] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A8A5[0m
[1;32muart:~$ [m[8D[J[00:25:47.266,052] [0m<dbg> lte_lc: event_handler_list_dispatch: Done[0m
[1;32muart:~$ [m[8D[J[00:25:47.365,875] [0m<dbg> at_monitor: at_monitor_task: AT notif: %XT3412: 3239999[0m
[1;32muart:~$ [m[8D[J[00:25:47.365,905] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3992d[0m
[1;32muart:~$ [m[8D[J[00:25:47.365,966] [0m<dbg> lte_lc: at_handler_xt3412: %XT3412 notification[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:25:47.465,972] [0m<dbg> at_monitor: at_monitor_task: AT notif: %XT3412: 0[0m
[1;32muart:~$ [m[8D[J[00:25:47.466,003] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3992d[0m
[1;32muart:~$ [m[8D[J[00:25:47.466,033] [0m<dbg> lte_lc: at_handler_xt3412: %XT3412 notification[0m
[1;32muart:~$ [m[8D[J[00:25:47.475,524] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031fc3, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:25:47.485,900] [0m<dbg> at_monitor: at_monitor_task: AT notif: +CSCON: 1[0m
[1;32muart:~$ [m[8D[J[00:25:47.485,931] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x39a7d[0m
[1;32muart:~$ [m[8D[J[00:25:47.485,961] [0m<dbg> lte_lc: at_handler_cscon: +CSCON notification[0m
[1;32muart:~$ [m[8D[J[00:25:47.486,083] [0m<dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=3[0m
[1;32muart:~$ [m[8D[J[00:25:47.486,114] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0003C989[0m
[1;32muart:~$ [m[8D[J[00:25:47.486,145] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00040D25[0m
[1;32muart:~$ [m[8D[J[00:25:47.486,175] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A8A5[0m
[1;32muart:~$ [m[8D[J[00:25:47.486,206] [0m<dbg> lte_lc: event_handler_list_dispatch: Done[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:25:47.667,907] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031f8b, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:25:47.667,999] [0m<dbg> lwm2m_security: load_credentials_to_modem: Existing credentials found on modem[0m
[1;32muart:~$ [m[8D[J[00:25:47.668,548] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031fcb, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:25:47.840,270] [0m<inf> net_lwm2m_engine: Connected, sock id 2[0m
[1;32muart:~$ [m[8D[J[00:25:47.841,003] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0x20031ff0, buflen:4[0m
[1;32muart:~$ [m[8D[J[00:25:47.842,407] [0m<dbg> net_lwm2m_rd_client: sm_send_registration: registration sent [<MY_IP>][0m
[1;32muart:~$ [m[8D[J[00:25:47.843,383] [0m<dbg> app_lwm2m_client: rd_client_event: Disconnected[0m
[1;32muart:~$ [m[8D[J[00:25:47.843,505] [0m<inf> net_lwm2m_rd_client: Stop LWM2M Client: <MY_ENDPOINT>[0m
[1;32muart:~$ [m[8D[J[00:25:47.845,031] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 17[0m
[1;32muart:~$ [m[8D[J[00:25:47.846,618] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 0[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:25:47.929,077] [0m<inf> app_lwm2m_client: Client connect to server[0m
[1;32muart:~$ [m[8D[J[00:25:47.929,168] [0m<inf> net_lwm2m_rd_client: Start LWM2M Client: <MY_ENDPOINT>[0m
[1;32muart:~$ [m[8D[J[00:25:47.929,443] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 1[0m
[1;32muart:~$ [m[8D[J[00:25:47.929,779] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 6[0m
[1;32muart:~$ [m[8D[J[00:25:47.929,809] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0x20032020, buflen:4[0m
[1;32muart:~$ [m[8D[J[00:25:47.929,840] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/0/0, level 3, buf:0x20032040, buflen:2[0m
[1;32muart:~$ [m[8D[J[00:25:47.929,931] [0m<inf> net_lwm2m_rd_client: RD Client started with endpoint '<MY_ENDPOINT>' with client lifetime 86400 using server object 0[0m
[1;32muart:~$ [m[8D[J[00:25:47.929,992] [0m<dbg> net_lwm2m_message_handling: lwm2m_parse_peerinfo: Parse url: coaps://<MY_URL>:5684[0m
[1;32muart:~$ [m[8D[J[00:25:47.930,633] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031fc3, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:25:48.056,610] [0m<inf> app_lwm2m_client: LwM2M is connecting to server[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:25:48.096,557] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031f8b, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:25:48.096,649] [0m<dbg> lwm2m_security: load_credentials_to_modem: Existing credentials found on modem[0m
[1;32muart:~$ [m[8D[J[00:25:48.097,198] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031fcb, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:25:48.258,239] [0m<inf> net_lwm2m_engine: Connected, sock id 2[0m
[1;32muart:~$ [m[8D[J[00:25:48.258,819] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0x20031ff0, buflen:4[0m
[1;32muart:~$ [m[8D[J[00:25:48.260,192] [0m<dbg> net_lwm2m_rd_client: sm_send_registration: registration sent [<MY_IP>][0m
[1;32muart:~$ [m[8D[J[00:25:48.262,390] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 8[0m
[1;32muart:~$ [m[8D[J[00:25:48.393,890] [0m<dbg> net_lwm2m_rd_client: do_registration_reply_cb: Registration callback (code:2.1)[0m
[1;32muart:~$ [m[8D[J[00:25:48.394,592] [0m<dbg> lte_lc: parse_psm: TAU: 3240 sec, active time: -1 sec[0m
[1;32muart:~$ [m[8D[J[00:25:48.394,622] [0m<dbg> lte_lc: lte_lc_psm_get: TAU: 3240 sec, active time: -1 sec[0m
[1;32muart:~$ [m[8D[J[00:25:48.394,653] [0m<dbg> lwm2m_sec_con_man: lwm2m_utils_update_rptau: PSM deactivated[0m
[1;32muart:~$ [m[8D[J[00:25:48.394,683] [0m<dbg> app_lwm2m_client: rd_client_event: Registration complete[0m
[1;32muart:~$ [m[8D[J[00:25:48.394,805] [0m<inf> net_lwm2m_rd_client: Registration Done (EP='XXXXXXX')[0m
[1;32muart:~$ [m[8D[J[00:25:48.394,989] [0m<dbg> net_lwm2m_message_handling: lwm2m_udp_receive: reply 0x2000d7c0 handled and removed[0m
[1;32muart:~$ [m[8D[J[00:25:48.395,050] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 9[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:25:48.477,661] [0m<inf> app_lwm2m_client: LwM2M is connected to server[0m
[1;32muart:~$ [m[8D[J[00:25:48.477,722] [0m<dbg> date_time: date_time_update_thread: Updating date time UTC...[0m
[1;32muart:~$ [m[8D[J[00:25:48.477,752] [0m<dbg> date_time: date_time_update_thread: Using previously obtained time[0m
[1;32muart:~$ [m[8D[J[00:25:48.477,783] [0m<inf> app_lwm2m_client: Obtained date-time from modem[0m
[1;32muart:~$ [m[8D[J[00:25:48.477,813] [0m<dbg> net_lwm2m_registry: lwm2m_engine_set: path:3/0/13, buf:0x2003275c, len:4[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:25:52.857,696] [0m<dbg> at_monitor: at_monitor_task: AT notif: +CSCON: 0[0m
[1;32muart:~$ [m[8D[J[00:25:52.857,727] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x39a7d[0m
[1;32muart:~$ [m[8D[J[00:25:52.857,757] [0m<dbg> lte_lc: at_handler_cscon: +CSCON notification[0m
[1;32muart:~$ [m[8D[J[00:25:52.857,910] [0m<dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=3[0m
[1;32muart:~$ [m[8D[J[00:25:52.857,910] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0003C989[0m
[1;32muart:~$ [m[8D[J[00:25:52.857,940] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00040D25[0m
[1;32muart:~$ [m[8D[J[00:25:52.857,971] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A8A5[0m
[1;32muart:~$ [m[8D[J[00:25:52.857,971] [0m<dbg> lte_lc: event_handler_list_dispatch: Done[0m
[1;32muart:~$ [m[8D[J[00:25:52.957,794] [0m<dbg> at_monitor: at_monitor_task: AT notif: %XT3412: 3239999[0m
[1;32muart:~$ [m[8D[J[00:25:52.957,855] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3992d[0m
[1;32muart:~$ [m[8D[J[00:25:52.957,885] [0m<dbg> lte_lc: at_handler_xt3412: %XT3412 notification[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:25:53.120,452] [0m<dbg> at_monitor: at_monitor_task: AT notif: %CESQ: 34,1,17,2[0m
[1;32muart:~$ [m[8D[J[00:25:53.120,513] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3bef9[0m
[1;32muart:~$ [m[8D[J[00:25:53.120,727] [0m<dbg> net_lwm2m_registry: lwm2m_engine_set: path:4/0/2, buf:0x2003989e, len:2[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:02.080,841] [0m<dbg> at_monitor: at_monitor_task: AT notif: %CESQ: 33,1,12,1[0m
[1;32muart:~$ [m[8D[J[00:26:02.080,902] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3bef9[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:07.393,768] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 9[0m
[1;32muart:~$ [m[8D[J[00:26:07.393,829] [0m<dbg> app_lwm2m_client: rd_client_event: Registration update started[0m
[1;32muart:~$ [m[8D[J[00:26:07.493,347] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 11[0m
[1;32muart:~$ [m[8D[J[00:26:07.493,865] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0x20031ff8, buflen:4[0m
[1;32muart:~$ [m[8D[J[00:26:07.494,018] [0m<dbg> net_lwm2m_rd_client: sm_send_registration: registration sent [<MY_IP>][0m
[1;32muart:~$ [m[8D[J[00:26:07.501,403] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 12[0m
[1;32muart:~$ [m[8D[J[00:26:07.604,492] [0m<dbg> at_monitor: at_monitor_task: AT notif: %XT3412: 0[0m
[1;32muart:~$ [m[8D[J[00:26:07.604,522] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3992d[0m
[1;32muart:~$ [m[8D[J[00:26:07.604,553] [0m<dbg> lte_lc: at_handler_xt3412: %XT3412 notification[0m
[1;32muart:~$ [m[8D[J[00:26:07.704,925] [0m<dbg> at_monitor: at_monitor_task: AT notif: +CSCON: 1[0m
[1;32muart:~$ [m[8D[J[00:26:07.704,986] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x39a7d[0m
[1;32muart:~$ [m[8D[J[00:26:07.705,017] [0m<dbg> lte_lc: at_handler_cscon: +CSCON notification[0m
[1;32muart:~$ [m[8D[J[00:26:07.705,169] [0m<dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=3[0m
[1;32muart:~$ [m[8D[J[00:26:07.705,200] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0003C989[0m
[1;32muart:~$ [m[8D[J[00:26:07.705,200] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00040D25[0m
[1;32muart:~$ [m[8D[J[00:26:07.705,230] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A8A5[0m
[1;32muart:~$ [m[8D[J[00:26:07.705,230] [0m<dbg> lte_lc: event_handler_list_dispatch: Done[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:08.495,117] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 12[0m
[1;32muart:~$ [m[8D[J[00:26:08.495,147] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State machine have timed out[0m
[1;32muart:~$ [m[8D[J[00:26:08.495,239] [0m<dbg> app_lwm2m_client: rd_client_event: Registration update failure![0m
[1;32muart:~$ [m[8D[J[00:26:08.495,300] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 1[0m
[1;32muart:~$ [m[8D[J[00:26:08.502,868] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 6[0m
[1;32muart:~$ [m[8D[J[00:26:08.502,899] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0x20032020, buflen:4[0m
[1;32muart:~$ [m[8D[J[00:26:08.502,960] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/0/0, level 3, buf:0x20032040, buflen:2[0m
[1;32muart:~$ [m[8D[J[00:26:08.503,021] [0m<inf> net_lwm2m_rd_client: RD Client started with endpoint '<MY_ENDPOINT>' with client lifetime 86400 using server object 0[0m
[1;32muart:~$ [m[8D[J[00:26:08.503,112] [0m<dbg> net_lwm2m_message_handling: lwm2m_parse_peerinfo: Parse url: coaps://<MY_URL>:5684[0m
[1;32muart:~$ [m[8D[J[00:26:08.503,784] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031fc3, buflen:1[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:08.641,876] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031f8b, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:26:08.641,998] [0m<dbg> lwm2m_security: load_credentials_to_modem: Existing credentials found on modem[0m
[1;32muart:~$ [m[8D[J[00:26:08.642,822] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031fcb, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:26:08.827,178] [0m<inf> net_lwm2m_engine: Connected, sock id 2[0m
[1;32muart:~$ [m[8D[J[00:26:08.827,911] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0x20031ff0, buflen:4[0m
[1;32muart:~$ [m[8D[J[00:26:08.829,315] [0m<dbg> net_lwm2m_rd_client: sm_send_registration: registration sent [<MY_IP>][0m
[1;32muart:~$ [m[8D[J[00:26:08.830,291] [0m<dbg> app_lwm2m_client: rd_client_event: Disconnected[0m
[1;32muart:~$ [m[8D[J[00:26:08.830,413] [0m<inf> net_lwm2m_rd_client: Stop LWM2M Client: <MY_ENDPOINT>[0m
[1;32muart:~$ [m[8D[J[00:26:08.831,481] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 17[0m
[1;32muart:~$ [m[8D[J[00:26:08.833,190] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 0[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:08.916,229] [0m<inf> app_lwm2m_client: Client connect to server[0m
[1;32muart:~$ [m[8D[J[00:26:08.916,290] [0m<inf> net_lwm2m_rd_client: Start LWM2M Client: <MY_ENDPOINT>[0m
[1;32muart:~$ [m[8D[J[00:26:08.916,564] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 1[0m
[1;32muart:~$ [m[8D[J[00:26:08.916,900] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 6[0m
[1;32muart:~$ [m[8D[J[00:26:08.916,931] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0x20032020, buflen:4[0m
[1;32muart:~$ [m[8D[J[00:26:08.916,992] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/0/0, level 3, buf:0x20032040, buflen:2[0m
[1;32muart:~$ [m[8D[J[00:26:08.917,053] [0m<inf> net_lwm2m_rd_client: RD Client started with endpoint '<MY_ENDPOINT>' with client lifetime 86400 using server object 0[0m
[1;32muart:~$ [m[8D[J[00:26:08.917,114] [0m<dbg> net_lwm2m_message_handling: lwm2m_parse_peerinfo: Parse url: coaps://<MY_URL>:5684[0m
[1;32muart:~$ [m[8D[J[00:26:08.917,999] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031fc3, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:26:09.040,771] [0m<inf> app_lwm2m_client: LwM2M is connecting to server[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:09.082,366] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031f8b, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:26:09.082,489] [0m<dbg> lwm2m_security: load_credentials_to_modem: Existing credentials found on modem[0m
[1;32muart:~$ [m[8D[J[00:26:09.083,099] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:0/1/2/0, level 3, buf:0x20031fcb, buflen:1[0m
[1;32muart:~$ [m[8D[J[00:26:09.207,244] [0m<inf> net_lwm2m_engine: Connected, sock id 2[0m
[1;32muart:~$ [m[8D[J[00:26:09.207,824] [0m<dbg> net_lwm2m_registry: lwm2m_engine_get: path:1/0/1/0, level 3, buf:0x20031ff0, buflen:4[0m
[1;32muart:~$ [m[8D[J[00:26:09.209,197] [0m<dbg> net_lwm2m_rd_client: sm_send_registration: registration sent [<MY_IP>][0m
[1;32muart:~$ [m[8D[J[00:26:09.211,395] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 8[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:13.028,656] [0m<dbg> at_monitor: at_monitor_task: AT notif: +CSCON: 0[0m
[1;32muart:~$ [m[8D[J[00:26:13.028,717] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x39a7d[0m
[1;32muart:~$ [m[8D[J[00:26:13.028,747] [0m<dbg> lte_lc: at_handler_cscon: +CSCON notification[0m
[1;32muart:~$ [m[8D[J[00:26:13.028,869] [0m<dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=3[0m
[1;32muart:~$ [m[8D[J[00:26:13.028,900] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0003C989[0m
[1;32muart:~$ [m[8D[J[00:26:13.028,930] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00040D25[0m
[1;32muart:~$ [m[8D[J[00:26:13.028,930] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A8A5[0m
[1;32muart:~$ [m[8D[J[00:26:13.028,961] [0m<dbg> lte_lc: event_handler_list_dispatch: Done[0m
[1;32muart:~$ [m[8D[J[00:26:13.128,784] [0m<dbg> at_monitor: at_monitor_task: AT notif: %XT3412: 3239999[0m
[1;32muart:~$ [m[8D[J[00:26:13.128,814] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3992d[0m
[1;32muart:~$ [m[8D[J[00:26:13.128,875] [0m<dbg> lte_lc: at_handler_xt3412: %XT3412 notification[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:15.004,791] [0m<dbg> at_monitor: at_monitor_task: AT notif: %XT3412: 0[0m
[1;32muart:~$ [m[8D[J[00:26:15.004,821] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x3992d[0m
[1;32muart:~$ [m[8D[J[00:26:15.004,852] [0m<dbg> lte_lc: at_handler_xt3412: %XT3412 notification[0m
[1;32muart:~$ [m[8D[J[00:26:15.105,010] [0m<dbg> at_monitor: at_monitor_task: AT notif: +CSCON: 1[0m
[1;32muart:~$ [m[8D[J[00:26:15.105,041] [0m<dbg> at_monitor: at_monitor_task: Dispatching to 0x39a7d[0m
[1;32muart:~$ [m[8D[J[00:26:15.105,072] [0m<dbg> lte_lc: at_handler_cscon: +CSCON notification[0m
[1;32muart:~$ [m[8D[J[00:26:15.105,224] [0m<dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=3[0m
[1;32muart:~$ [m[8D[J[00:26:15.105,224] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0003C989[0m
[1;32muart:~$ [m[8D[J[00:26:15.105,255] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00040D25[0m
[1;32muart:~$ [m[8D[J[00:26:15.105,285] [0m<dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A8A5[0m
[1;32muart:~$ [m[8D[J[00:26:15.105,316] [0m<dbg> lte_lc: event_handler_list_dispatch: Done[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:15.150,085] [0m<dbg> net_lwm2m_rd_client: do_registration_reply_cb: Registration callback (code:2.1)[0m
[1;32muart:~$ [m[8D[J[00:26:15.150,909] [0m<dbg> lte_lc: parse_psm: TAU: 3240 sec, active time: -1 sec[0m
[1;32muart:~$ [m[8D[J[00:26:15.150,970] [0m<dbg> lte_lc: lte_lc_psm_get: TAU: 3240 sec, active time: -1 sec[0m
[1;32muart:~$ [m[8D[J[00:26:15.151,000] [0m<dbg> lwm2m_sec_con_man: lwm2m_utils_update_rptau: PSM deactivated[0m
[1;32muart:~$ [m[8D[J[00:26:15.151,000] [0m<dbg> app_lwm2m_client: rd_client_event: Registration complete[0m
[1;32muart:~$ [m[8D[J[00:26:15.151,153] [0m<inf> net_lwm2m_rd_client: Registration Done (EP='XXXXXXX')[0m
[1;32muart:~$ [m[8D[J[00:26:15.151,336] [0m<dbg> net_lwm2m_message_handling: lwm2m_udp_receive: reply 0x2000d7c0 handled and removed[0m
[1;32muart:~$ [m[8D[J[00:26:15.151,397] [0m<dbg> net_lwm2m_rd_client: lwm2m_rd_client_service: State: 9[0m
[1;32muart:~$ [m[8D[J[00:26:15.236,083] [0m<inf> app_lwm2m_client: LwM2M is connected to server[0m
[1;32muart:~$ [m[8D[J[00:26:15.236,145] [0m<dbg> date_time: date_time_update_thread: Updating date time UTC...[0m
[1;32muart:~$ [m[8D[J[00:26:15.236,175] [0m<dbg> date_time: date_time_update_thread: Using previously obtained time[0m
[1;32muart:~$ [m[8D[J[00:26:15.236,206] [0m<inf> app_lwm2m_client: Obtained date-time from modem[0m
[1;32muart:~$ [m[8D[J[00:26:15.236,236] [0m<dbg> net_lwm2m_registry: lwm2m_engine_set: path:3/0/13, buf:0x2003275c, len:4[0m
[1;32muart:~$ [m[8D[J[1;32muart:~$ [m[8D[J[00:26:17.922,058] [0m<dbg> net_lwm2m_observation: engine_observe_node_init: OBSERVER ADDED 10351/0/50/0(3)[0m
[1;32muart:~$ [m[8D[J[00:26:17.922,149] [0m<dbg> net_lwm2m_observation: engine_observe_node_init: token:'afd3250c8d52644c' addr:<MY_IP>[0m
[1;32muart:~$ [m[8D[J[00:26:17.922,180] [0m<dbg> net_lwm2m_registry: lwm2m_engine_set: path:10351/0/50, buf:0x20031e9f, len:1[0m

After Registration update failure! we see lwm2m_utils_update_rptau: PSM deactivated. Our assumption is that in this situation the board previously went into LTE_OFFLINE and stayed offline.

It seems like we are making some progress here!

RE: Help with LTE connection after loss of connection

Matias Marti — Tue, 10 Sep 2024 09:42:34 GMT

Hello lobaro-theo ,

We have not used v2.5.0, only 2.3.0 and now 2.6.0. Thank you for sharing your findings on v2.5.0. My guess is that there might have been new config values that have been added to 2.6.0 that are discarded by 2.5.0 (that is, if you prj.conf looks the same).