subscribing in Assert tracker v2

RE: subscribing in Assert tracker v2

Didrik Rokhaug — Fri, 05 Nov 2021 13:01:35 GMT

Thanks for the summary, and sorry for the slow response.

Have you tried to connect to other brokers (i.e. not AWS)?

E.g. if you run the mqtt_simple sample (with PSM), do you see the same problem where the client is disconnected from the broker after being in PSM for > 300s?

Attached is a slightly modified version of the mqtt_simple (from NCS v1.6.1) sample that connects to test.mosquitto.org with a keepalive period of 600s, and PSM. It will also print each time it calls mqtt_live, so it is easy to keep track of when it sends MQTT keepalive messages.

devzone.nordicsemi.com/.../mqtt_5F00_simple.zip

On my end, it successfully sends a keepalive message after 10 minutes, so at least on my setup, it works as it should.

If it doesn't work, can you share the application and modem log?

RE: subscribing in Assert tracker v2

Mustafa — Tue, 02 Nov 2021 10:52:03 GMT

one thing I forget to mention is that this problem occurs only when PSM is enabled
if PSM is disabled, the server receives always message from the device.

RE: subscribing in Assert tracker v2

Mustafa — Tue, 02 Nov 2021 10:48:34 GMT

Hey Didrik,

You are right this issue took a long time. here is the summarize of the problem when CONFIG_MQTT_KEEPALIVE is set for more than 300 sec then the server ( AWS IoT ) doesn't receive any message from the device, even though the device log shows that message is sent successfully.

we tried with T-mobile and KPN in NL and both are almost the same except in the T-mobile network the device lost connection after 300 sec when CONFIG_MQTT_KEEPALIVE > 300 sec. but in the KPN network the device doesn't show any error. In both networks, the server doesn't receive anything after 300 sec

our project is based on Low power consumption so we need to set CONFIG_MQTT_KEEPALIVE to a max of AWS limit and that is 1200 sec. but it doesn't work when it is initialized for more than 300 sec.

we use

SDK = nrf 1.6.1,

modem version 1.3.0
Mqtt server: AWS Iot mqtt

LTE-M network: KPN and T-mobile in NL

app: asset_tracker_v2

RE: subscribing in Assert tracker v2

Didrik Rokhaug — Tue, 02 Nov 2021 10:32:43 GMT

Here is what the modem team said:

With given information I am not able to comment anything very meaningful. TLS connection is established and UE sends 708 bytes to server. This is acked by the server, but nothing more really. Seems that server is not responding or data is lost somewhere in the path.

After twenty minutes there are weird TCP transmission to unseen segments. I think the log is not complete and some parts are missing. TCP segment from UE to server jumps from 185 to 3018 which is not possible.

At this point, I feel like the ticket has gone on long enough that it is time to take a tep back and try to get an overview of where we are. Could you try to sum up the problem you are seeing?

What are you trying to do, and what is happening?

What application FW are you suing, which SDK version is it based on, and what modem FW version are you using?

RE: subscribing in Assert tracker v2

Mustafa — Sun, 24 Oct 2021 16:36:11 GMT

Hey Didrik, sorry for my late message. I was actually struggling with GPS timeout that sometimes tracker keeps searching for GPS fix for more than one hour and GPS timeout is already adjusted on 60 sec but that is for another issue. For now, I've tested the devices with/without PSM and I've noticed that without PSM the connection with the server still opens but the device sends an update message per 26 min instead of 60 min since the settings are adjusted to 3600 sec. Here below are the traces files

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_10_2D00_24T07_2D00_58_2D00_11.071Z-without-psm.rar

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_10_2D00_24T14_2D00_09_2D00_26.958Z-with-psm.rar

RE: subscribing in Assert tracker v2

Didrik Rokhaug — Thu, 21 Oct 2021 12:03:37 GMT

Hi, have you been able to capture traces without PSM yet?

RE: subscribing in Assert tracker v2

Didrik Rokhaug — Thu, 14 Oct 2021 15:49:26 GMT

The KPN trace looks better this time, but it doesn't look like it captured the device waking up. The trace ended only a minute after the SUPL session completed. And the SUPL session ended just a couple of seconds after the last packet sent to the cloud. The whole trace lasts for only a bit less than 2 minutes.

The T Mobile trace on the other hand looks like have captured the issue. But, it looks like the device is still requesting PSM, even though the application doesn't request it. This is probably because the modem has the PSM settings stored. The easiest way to tell the modem not to use PSM is to flash the at_cmd sample, send AT+CPSMS=0 followed by AT+CFUN=0.

RE: subscribing in Assert tracker v2

Mustafa — Wed, 13 Oct 2021 22:02:21 GMT

Hey Didrik, thanks for your reply. I did some experiments with two different network operators. I disabled PSM and changed Mqtt_keep alive to 400sec.

In the first operator ( KPN in NL ) the server doesn't receive any data after 300 sec even device shows that data is sent successfully.

The second operator ( T-Mobile in NL): the device gets a timeout after 320sec and then it tries to establish the connection again with the server and every 320sec it gets event Timeout and re-initializes connection with server-side.

Here below are the trace files per operator, hopefully, that you can find the problem.

KPN

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_10_2D00_13T21_2D00_39_2D00_09.599Z-KPN.rar

T Mobile

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_10_2D00_13T21_2D00_20_2D00_33.087Z-TMobile.rar

thanks in advance!

RE: subscribing in Assert tracker v2

Didrik Rokhaug — Tue, 12 Oct 2021 14:53:16 GMT

There were some problems with the trace, so I was not able to take a proper look at the IP packets.

However, I couldn't see anything that looked wrong in your trace. And in both the trace and the log it looks like the communication with the cloud continued as it should?

Also, when you take a modem trace, it is nice if you restart the device after starting capturing the trace, so that we can see the startup sequence as well.

RE: subscribing in Assert tracker v2

Mustafa — Mon, 11 Oct 2021 20:03:06 GMT

Hey Didrik, I disabled PSM and tried again but it seems that it is the same, no difference. After 300 sec no data was sent to the server-side, even it shows in the logs that data is sent successfully but no data is received by server-side. I attached here the trace file and the log file as well, hoping that you can figure out what the problem is.

Thanks in advance.

[00:00:00.223,754] [1;33m<wrn> cloud_codec: set alarm ---> 1[0m
[00:00:00.257,659] [0m<dbg> cloud_module.state_set: State: STATE_LTE_DISCONNECTED[0m
[00:00:00.267,822] [0m<dbg> cloud_module.sub_state_set: Sub state: SUB_STATE_CLOUD_DISCONNECTED[0m
[00:00:00.287,780] [1;33m<wrn> data_module: Device configuration loaded from flash[0m
[00:00:00.298,461] [1;33m<wrn> data_module: active_mode = 0[0m
[00:00:00.306,518] [1;33m<wrn> data_module: active_wait_timeout = 300[0m
[00:00:00.315,399] [1;33m<wrn> data_module: movement_resolution = 60[0m
[00:00:00.327,087] [1;33m<wrn> data_module: movement_timeout = 1000[0m
[00:00:00.335,968] [1;33m<wrn> data_module: gps_timeout = 60[0m
[00:00:00.344,024] [1;33m<wrn> data_module: accelerometer_threshold = 5.000000[0m
[00:00:00.359,924] [1;33m<wrn> app_module: the certificates are found[0m
[00:00:00.367,462] [0m<inf> event_manager: APP_EVT_START[0m
[00:00:00.373,535] [0m<dbg> gps_module.state_set: State: STATE_INIT[0m
[00:00:00.354,766] [0m<dbg> sensor_module.state_set: State: STATE_INIT[0m
[00:00:00.524,230] [0m<inf> event_manager: DATA_EVT_CONFIG_INIT[0m
[00:00:00.530,975] [0m<dbg> gps_module.state_set: State transition STATE_INIT --> STATE_RUNNING[0m
[00:00:00.542,541] [0m<inf> app_module: Device mode: Passive[0m
[00:00:00.548,675] [0m<inf> app_module: Start movement timeout: 1000 seconds interval[0m
[00:00:00.557,098] [0m<inf> app_module: 60 seconds until movement can trigger a new data sample/publication[0m
[00:00:00.567,932] [0m<dbg> sensor_module.state_set: State transition STATE_INIT --> STATE_RUNNING[0m
[00:00:00.697,998] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTING[0m
[00:00:01.783,447] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
[00:00:01.801,055] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
[00:00:02.493,225] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
[00:00:02.500,549] [0m<inf> event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
[00:00:02.507,995] [0m<dbg> cloud_module.state_set: State transition STATE_LTE_DISCONNECTED --> STATE_LTE_CONNECTED[0m
[00:00:02.519,165] [0m<dbg> cloud_module.connect_cloud: Connecting to cloud[0m
[00:00:02.526,763] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
[00:00:02.535,369] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
[00:00:02.545,104] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_CONNECTING[0m
[00:00:02.554,229] [0m<dbg> cloud_module.cloud_wrap_event_handler: CLOUD_WRAP_EVT_CONNECTING[0m
[00:00:02.563,415] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
[00:00:06.347,198] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_CONNECTED[0m
[00:00:06.545,806] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_READY[0m
[00:00:06.570,129] [0m<dbg> cloud_module.cloud_wrap_event_handler: CLOUD_WRAP_EVT_CONNECTED[0m
[00:00:06.606,109] [0m<inf> event_manager: CLOUD_EVT_CONNECTED[0m
[00:00:06.613,922] [0m<dbg> cloud_module.sub_state_set: Sub state transition SUB_STATE_CLOUD_DISCONNECTED --> SUB_STATE_CLOUD_CONNECTED[0m
[00:00:06.855,651] [0m<inf> event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
[00:00:06.863,189] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS, MOD_STAT)[0m
[00:00:06.904,235] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
[00:00:06.910,369] [0m<dbg> gps_module.sub_state_set: Sub state transition SUB_STATE_IDLE --> SUB_STATE_SEARCH[0m
[00:00:06.921,173] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_SEARCH_STARTED[0m
[00:00:06.929,229] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_AGPS_DATA_NEEDED[0m
[00:00:06.937,500] [0m<inf> event_manager: GPS_EVT_AGPS_NEEDED[0m
[00:00:06.944,427] [0m<dbg> sensor_module.environmental_data_get: No external sensors, submitting dummy sensor data[0m
[00:00:06.958,984] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
[00:00:06.968,475] [0m<inf> agps: SUPL is initialized[0m
[00:00:07.064,544] [0m<inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY[0m
[00:00:07.147,796] [0m<inf> agps: Starting SUPL session[0m
[00:00:07.216,156] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
[00:00:07.245,758] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_modem_dynamic_buffer: Entry: 1 of 2 in dynamic modem buffer filled[0m
[00:00:07.558,776] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
[00:00:07.587,951] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_bat_buffer: Entry: 1 of 2 in battery buffer filled[0m
[00:00:07.892,944] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_BLOCKED[0m
[00:00:09.315,582] [0m<inf> agps: SUPL session finished successfully[0m
[00:00:22.259,094] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_UNBLOCKED[0m
[00:00:35.329,620] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_BLOCKED[0m
[00:01:00.567,718] [0m<inf> event_manager: APP_EVT_ACTIVITY_DETECTION_ENABLE[0m
[00:01:21.968,444] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
[00:01:22.073,333] [0m<inf> event_manager: DATA_EVT_DATA_SEND[0m
[00:01:22.080,322] [0m<dbg> cloud_codec.cloud_codec_encode_batch_data: No data to encode, JSON string empty...[0m
[00:01:22.184,082] [1;33m<wrn> cloud_module:  Data sent, data pointer: 0x200201e0[0m
[00:01:22.192,199] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:01:41.464,813] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_SEARCH_TIMEOUT[0m
[00:01:41.472,900] [0m<inf> event_manager: GPS_EVT_TIMEOUT[0m
[00:01:41.479,156] [0m<inf> event_manager: GPS_EVT_INACTIVE[0m
[00:01:41.485,473] [0m<dbg> gps_module.sub_state_set: Sub state transition SUB_STATE_SEARCH --> SUB_STATE_IDLE[0m
[00:01:41.496,337] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
[00:01:41.503,387] [0m<dbg> cloud_codec.cloud_codec_encode_data: No data to encode, JSON string empty...[0m
[00:07:35.488,983] [0m<inf> event_manager: UI_EVT_BUTTON_ALARM_DATA_READY[0m
[00:07:35.496,520] [0m<inf> event_manager: UI_EVT_BUTTON_DATA_READY[0m
[00:07:35.503,662] [0m<inf> event_manager: APP_EVT_DATA_GET_ALL[0m
[00:07:35.510,498] [0m<inf> app_module: Device mode: Passive[0m
[00:07:35.516,693] [0m<inf> app_module: Start movement timeout: 1000 seconds interval[0m
[00:07:35.525,207] [0m<inf> app_module: 60 seconds until movement can trigger a new data sample/publication[0m
[00:07:35.535,888] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS)[0m
[00:07:35.546,752] [1;33m<wrn> cloud_codec: set alarm ---> 1[0m
[00:07:35.556,518] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_ui_buffer: Entry: 1 of 2 in UI buffer filled[0m
[00:07:35.570,800] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_ui_buffer: Entry: 2 of 2 in UI buffer filled[0m
[00:07:35.606,475] [0m<inf> event_manager: DATA_EVT_UI_DATA_READY[0m
[00:07:35.613,403] [0m<inf> event_manager: DATA_EVT_UI_DATA_READY[0m
[00:07:35.620,330] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
[00:07:35.643,585] [0m<dbg> gps_module.sub_state_set: Sub state transition SUB_STATE_IDLE --> SUB_STATE_SEARCH[0m
[00:07:35.654,571] [0m<dbg> sensor_module.environmental_data_get: No external sensors, submitting dummy sensor data[0m
[00:07:35.665,771] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
[00:07:35.690,826] [0m<inf> event_manager: DATA_EVT_UI_DATA_SEND[0m
[00:07:35.707,885] [0m<inf> event_manager: UI_EVT_BUTTON_ALARM_DATA_READY[0m
[00:07:35.699,401] [0m<dbg> cloud_module.ui_data_send: UI sent, data pointer: 0x2001fbf8[0m
[00:07:35.716,247] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:07:35.723,052] [1;33m<wrn> cloud_codec: set alarm ---> 1[0m
[00:07:35.729,187] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_ui_buffer: Entry: 0 of 2 in UI buffer filled[0m
[00:07:35.830,505] [0m<inf> event_manager: DATA_EVT_UI_DATA_READY[0m
[00:07:35.852,386] [0m<inf> event_manager: DATA_EVT_UI_DATA_SEND[0m
[00:07:35.863,189] [0m<dbg> cloud_module.ui_data_send: UI sent, data pointer: 0x2001fc40[0m
[00:07:35.875,549] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:07:36.300,201] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
[00:07:36.308,563] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_modem_dynamic_buffer: Entry: 2 of 2 in dynamic modem buffer filled[0m
[00:07:36.407,684] [0m<inf> event_manager: UI_EVT_BUTTON_ALARM_DATA_READY[0m
[00:07:36.425,537] [1;33m<wrn> cloud_codec: set alarm ---> 0[0m
[00:07:36.469,940] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_ui_buffer: Entry: 1 of 2 in UI buffer filled[0m
[00:07:36.487,152] [0m<inf> event_manager: DATA_EVT_UI_DATA_READY[0m
[00:07:36.508,880] [0m<inf> event_manager: DATA_EVT_UI_DATA_SEND[0m
[00:07:36.517,120] [0m<dbg> cloud_module.ui_data_send: UI sent, data pointer: 0x2001fc00[0m
[00:07:36.528,594] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:07:36.579,010] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
[00:07:36.586,791] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_bat_buffer: Entry: 2 of 2 in battery buffer filled[0m
[00:07:36.639,862] [0m<inf> event_manager: UI_EVT_BUTTON_ALARM_DATA_READY[0m
[00:07:36.647,430] [1;33m<wrn> cloud_codec: set alarm ---> 1[0m
[00:07:36.653,625] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_ui_buffer: Entry: 2 of 2 in UI buffer filled[0m
[00:07:36.665,008] [0m<inf> event_manager: DATA_EVT_UI_DATA_READY[0m
[00:07:36.684,600] [0m<inf> event_manager: DATA_EVT_UI_DATA_SEND[0m
[00:07:36.700,531] [0m<dbg> cloud_module.ui_data_send: UI sent, data pointer: 0x2001fc00[0m
[00:07:36.709,320] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:08:05.594,970] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_UNBLOCKED[0m
[00:08:10.650,787] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_BLOCKED[0m
[00:08:29.078,704] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_UNBLOCKED[0m
[00:08:34.143,585] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_BLOCKED[0m
[00:08:35.535,797] [0m<inf> event_manager: APP_EVT_ACTIVITY_DETECTION_ENABLE[0m
[00:08:50.678,161] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
[00:08:50.711,395] [0m<inf> event_manager: DATA_EVT_DATA_SEND[0m
[00:08:50.718,383] [0m<dbg> cloud_codec.cloud_codec_encode_batch_data: No data to encode, JSON string empty...[0m
[00:08:50.733,062] [1;33m<wrn> cloud_module:  Data sent, data pointer: 0x2001fd80[0m
[00:08:50.741,271] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:08:52.627,044] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_UNBLOCKED[0m
[00:08:56.790,222] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_BLOCKED[0m
[00:09:26.429,962] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_SEARCH_TIMEOUT[0m
[00:09:26.438,018] [0m<inf> event_manager: GPS_EVT_TIMEOUT[0m
[00:09:26.444,305] [0m<inf> event_manager: GPS_EVT_INACTIVE[0m
[00:09:26.450,592] [0m<dbg> gps_module.sub_state_set: Sub state transition SUB_STATE_SEARCH --> SUB_STATE_IDLE[0m
[00:09:26.461,761] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
[00:09:26.468,780] [0m<dbg> cloud_codec.cloud_codec_encode_data: No data to encode, JSON string empty...[0m

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_10_2D00_11T19_2D00_45_2D00_20.101Z.rar

RE: subscribing in Assert tracker v2

Didrik Rokhaug — Mon, 11 Oct 2021 11:16:31 GMT

When using the asset_tracker_v2, you can set CONFIG_MODEM_AUTO_REQUEST_POWER_SAVING_FEATURES=n.

That should stop the application from requesting PSM.

RE: subscribing in Assert tracker v2

Mustafa — Mon, 11 Oct 2021 09:32:27 GMT

Hello Didrik,

What is the best way to disable PSM in the prj.conf ?

Thanks

RE: subscribing in Assert tracker v2

Didrik Rokhaug — Mon, 11 Oct 2021 09:18:50 GMT

Hi,

Could you try to disable PSM, to see if that changes things?

Best regards,

Didrik

RE: subscribing in Assert tracker v2

Albrecht Markus Schellenberger — Fri, 08 Oct 2021 13:52:01 GMT

[quote user="Mustafaq"]Actually I'm still wondering about the reason to close the TCP connection with server-side. It supposes to keep the connection alive because CONFIG_MQTT_KEEPALIVE = 1200. even I tried to reduce this time but it always closes the connection after 320 seconds ( any value above 320sec causes CLOUD_TIMEOUT event).[/quote]

Thanks a lot for your feedback, Mustafa! That is a good and interesting observation. I wonder if maybe the NAT rules time-out, making the server not recognise the client anymore? I have to check this with our experts. I’ll be on vacation next week, but I asked my colleague Didrik Rokhaug to watch this ticket.

Regards,

Markus

RE: subscribing in Assert tracker v2

Mustafa — Fri, 08 Oct 2021 12:14:49 GMT

Thank you Markus for your answer, Actually I'm still wondering about the reason to close the TCP connection with server-side. It supposes to keep the connection alive because CONFIG_MQTT_KEEPALIVE = 1200. even I tried to reduce this time but it always closes the connection after 320 seconds ( any value above 320sec causes CLOUD_TIMEOUT event).

RE: subscribing in Assert tracker v2

Albrecht Markus Schellenberger — Fri, 08 Oct 2021 11:30:10 GMT

Hello again,

I already got some feedback from our modem team :-)

Analysis from log:

Application has configured PSM. Sleep period 1 hour, active time 2 seconds
00:00:00.206512 L23_AT_STRING AT_STRING => +CPSMS=1,,,"00100001","00000001"

UE sends TLS data that is acked by server. This is last data transmission.

40 sec after data transmission RRC connection is released and after 2 seconds active time the modem falls to PSM and is not listening to network.

00:00:49.655944 ERRC_PDU_TYPE_DL_DCCH_3 ERRC PDU: RRCConnectionRelease
00:00:52.933563 EMM_STATE_CHANGE : EMM_REG_NORMAL_SERVICE => EMM_REG_NO_CELL_AVAILABLE

After 20 minutes from last user data, the application tries to send more data, but TCP connection is already closed by the server.

So, PSM prevents the client from receiving DL data. Our recommendation is that you should start with disabling PSM completely. Afterwards, you could adjust the active time to the servers response time.

Regards,

Markus

RE: subscribing in Assert tracker v2

Albrecht Markus Schellenberger — Fri, 08 Oct 2021 06:18:28 GMT

Hello Mustafa,

My apologies for the delayed reply. Markus Tacker is on vacation currently. I will forward the trace to our modem team for further analysis and keep you posted.

Regards,

Markus

RE: subscribing in Assert tracker v2

Mustafa — Sun, 03 Oct 2021 16:18:09 GMT

Hey Markus, Thanks for ur answer. I attached the new binary file of the modem trace. Unfortunately, I couldn't find a way to verify the binary file.
Actually, I tried to use another sim card from T-Mobile in NL and it seems that the Cloud timeout event is triggered every time the application tries to ping Mqtt broker ( AWS ), in my case every 20 min since

CONFIG_MQTT_KEEPALIVE=1200

App's Log

[00:00:00.254,913] [0m<inf> event_manager: APP_EVT_START[0m
[00:00:00.260,772] [0m<dbg> gps_module.state_set: State: STATE_INIT[0m
[00:00:00.268,341] [0m<dbg> cloud_module.state_set: State: Unknown[0m
[00:00:00.275,085] [0m<dbg> cloud_module.sub_state_set: Sub state: SUB_STATE_CLOUD_DISCONNECTED[0m
///////////////////////////////////////////////////////////////////////////////////////////
[00:00:00.287,445] [1;33m<wrn> data_module: Device configuration loaded from flash[0m
[00:00:00.295,654] [1;33m<wrn> data_module: active_mode = 0[0m
[00:00:00.301,818] [1;33m<wrn> data_module: active_wait_timeout = 300[0m
[00:00:00.308,868] [1;33m<wrn> data_module: movement_resolution = 60[0m
[00:00:00.315,765] [1;33m<wrn> data_module: movement_timeout = 3600[0m
[00:00:00.322,601] [1;33m<wrn> data_module: gps_timeout = 60[0m
[00:00:00.328,887] [1;33m<wrn> data_module: accelerometer_threshold = 5.000000[0m
///////////////////////////////////////////////////////////////////////////////////////
[00:00:00.336,944] [0m<inf> event_manager: DATA_EVT_CONFIG_INIT[0m
[00:00:00.344,024] [0m<inf> event_manager: MODEM_EVT_INITIALIZED[0m
[00:00:00.351,013] [0m<dbg> gps_module.lna_configure: MAGPIO command: AT%XMAGPIO=1,0,0,1,1,1574,1577[0m
[00:00:00.360,839] [0m<dbg> gps_module.lna_configure: COEX0 command: AT%XCOEX0=1,1,1565,1586[0m
[00:00:00.370,025] [0m<dbg> sensor_module.state_set: State: STATE_INIT[0m
[00:00:00.379,241] [0m<dbg> sensor_module.state_set: State transition STATE_INIT --> STATE_RUNNING[0m
[00:00:00.401,550] [0m<dbg> gps_module.state_set: State transition STATE_INIT --> STATE_RUNNING[0m
[00:00:00.391,143] [0m<dbg> cloud_module.state_set: State transition Unknown --> STATE_LTE_DISCONNECTED[0m
[00:00:00.705,078] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTING[0m
[00:00:06.509,613] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
[00:00:06.517,364] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
[00:00:07.289,825] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
[00:00:07.302,642] [0m<inf> event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
[00:00:07.310,272] [0m<dbg> cloud_module.state_set: State transition STATE_LTE_DISCONNECTED --> STATE_LTE_CONNECTED[0m
[00:00:07.321,502] [0m<dbg> cloud_module.connect_cloud: Connecting to cloud[0m
[00:00:07.334,686] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
[00:00:07.343,383] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
[00:00:07.353,240] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_CONNECTING[0m
[00:00:07.362,396] [0m<dbg> cloud_module.cloud_wrap_event_handler: CLOUD_WRAP_EVT_CONNECTING[0m
[00:00:07.371,582] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
[00:00:10.293,853] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_CONNECTED[0m
[00:00:10.467,620] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_READY[0m
[00:00:10.476,409] [0m<dbg> cloud_module.cloud_wrap_event_handler: CLOUD_WRAP_EVT_CONNECTED[0m
[00:00:10.513,031] [0m<inf> event_manager: CLOUD_EVT_CONNECTED[0m
[00:00:10.520,996] [0m<dbg> cloud_module.sub_state_set: Sub state transition SUB_STATE_CLOUD_DISCONNECTED --> SUB_STATE_CLOUD_CONNECTED[0m
[00:00:10.778,289] [0m<inf> event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
[00:00:10.788,818] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, MOD_STAT)[0m
[00:00:10.801,849] [0m<dbg> sensor_module.environmental_data_get: No external sensors, submitting dummy sensor data[0m
[00:00:10.813,110] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
[00:00:10.904,998] [0m<inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY[0m
[00:00:10.995,849] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
[00:00:11.004,425] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_modem_dynamic_buffer: Entry: 1 of 2 in dynamic modem buffer filled[0m
[00:00:11.146,301] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
[00:00:11.172,119] [0m<inf> event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
[00:00:11.154,266] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_bat_buffer: Entry: 1 of 2 in battery buffer filled[0m
[00:00:11.191,711] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
[00:00:11.219,055] [0m<inf> event_manager: DATA_EVT_NEIGHBOR_CELLS_DATA_SEND[0m
[00:00:11.294,708] [0m<inf> event_manager: DATA_EVT_DATA_SEND[0m
[00:00:11.302,612] [0m<dbg> cloud_codec.cloud_codec_encode_batch_data: No data to encode, JSON string empty...[0m
[00:00:11.323,852] [0m<dbg> cloud_module.neighbor_cells_data_send: Neighbor cell data sent, data pointer: 0x2001e748[0m
[00:00:11.335,266] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:00:11.349,334] [0m<dbg> cloud_module.data_send: Data sent, data pointer: 0x2001ec58[0m
[00:00:11.358,123] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:01:00.343,994] [0m<inf> event_manager: APP_EVT_ACTIVITY_DETECTION_ENABLE[0m
[00:20:11.383,575] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_DISCONNECTED[0m
[00:20:11.393,524] [0m<dbg> cloud_module.cloud_wrap_event_handler: CLOUD_WRAP_EVT_DISCONNECTED[0m
[00:20:11.405,303] [0m<inf> event_manager: CLOUD_EVT_DISCONNECTED[0m
[00:20:11.414,367] [0m<dbg> cloud_module.sub_state_set: Sub state transition SUB_STATE_CLOUD_CONNECTED --> SUB_STATE_CLOUD_DISCONNECTED[0m
[00:20:11.427,459] [0m<dbg> cloud_module.connect_check_work_fn: Cloud connection timeout occurred[0m
[00:20:11.437,133] [0m<inf> event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
[00:20:11.444,824] [0m<dbg> cloud_module.connect_cloud: Connecting to cloud[0m
[00:20:11.452,423] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
[00:20:11.461,090] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
[00:20:11.470,916] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_CONNECTING[0m
[00:20:11.480,133] [0m<dbg> cloud_module.cloud_wrap_event_handler: CLOUD_WRAP_EVT_CONNECTING[0m
[00:20:11.492,126] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
[00:20:14.386,016] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_CONNECTED[0m
[00:20:14.591,369] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_READY[0m
[00:20:14.600,158] [0m<dbg> cloud_module.cloud_wrap_event_handler: CLOUD_WRAP_EVT_CONNECTED[0m
[00:20:14.613,830] [0m<inf> event_manager: CLOUD_EVT_CONNECTED[0m
[00:20:14.623,626] [0m<dbg> cloud_module.sub_state_set: Sub state transition SUB_STATE_CLOUD_DISCONNECTED --> SUB_STATE_CLOUD_CONNECTED[0m
[00:20:14.636,810] [0m<inf> event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
[00:20:14.644,561] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS)[0m
[00:20:14.656,707] [0m<dbg> sensor_module.environmental_data_get: No external sensors, submitting dummy sensor data[0m
[00:20:14.667,999] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
[00:20:14.761,810] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
[00:20:14.770,355] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_modem_dynamic_buffer: Entry: 2 of 2 in dynamic modem buffer filled[0m
[00:20:14.847,076] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
[00:20:14.874,450] [0m<inf> event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
[00:20:14.856,140] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_bat_buffer: Entry: 2 of 2 in battery buffer filled[0m
[00:20:14.895,019] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
[00:20:14.922,393] [0m<inf> event_manager: DATA_EVT_NEIGHBOR_CELLS_DATA_SEND[0m
[00:20:14.954,986] [0m<inf> event_manager: DATA_EVT_DATA_SEND[0m
[00:20:14.962,921] [0m<dbg> cloud_codec.cloud_codec_encode_batch_data: No data to encode, JSON string empty...[0m
[00:20:14.983,612] [0m<dbg> cloud_module.neighbor_cells_data_send: Neighbor cell data sent, data pointer: 0x2001e748[0m
[00:20:14.995,666] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:20:15.019,470] [0m<dbg> cloud_module.data_send: Data sent, data pointer: 0x2001e688[0m
[00:20:15.028,228] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m

I've tried the Assert tracker v2 of SDK v1.7.1 and SDK v1.6.1 as well. They both gave the same result.

The configuration of TAU and active timer is

CONFIG_LTE_PSM_REQ_RPTAU="00100001" # 1hour

CONFIG_LTE_PSM_REQ_RAT="00000001" # 2 sec

the values of timers are confirmed by this command

AT+CEREG?

+CEREG: 5,5,"0106","00277416",7,,,"00000001","00100001"

OK
devzone.nordicsemi.com/.../trace_2D00_2021_2D00_10_2D00_03T15_2D00_01_2D00_15.377Z.rar

RE: subscribing in Assert tracker v2

Markus Tacker (he/him) — Mon, 27 Sep 2021 12:39:39 GMT

Unfortunately, the trace was corrupted. This can happen if using a defective USB cable, but also could be cause by an outdated firmware on the onboard Segger chip.

If you use a DK, you can update the firmware on the onboard Segger chip, which should improve the UART performance. You can use a tool called J-Link Configurator to do this. The tool ships with the J-Link software bundle, so there's a good chance that you have already installed it. If not, you can get it here: https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack

Get v7.52 or newer.

To verify that a trace is not corrupted, you can use the nRF Trace Collector. It has the option (and instructions how to) both collect traces and view them in Wireshark. If what you see in Wireshark makes sense, that's a good sign.

RE: subscribing in Assert tracker v2

Markus Tacker (he/him) — Thu, 23 Sep 2021 15:46:18 GMT

Thanks!

RE: subscribing in Assert tracker v2

Mustafa — Thu, 23 Sep 2021 15:44:41 GMT

it is version 1.3.0

RE: subscribing in Assert tracker v2

Markus Tacker (he/him) — Thu, 23 Sep 2021 15:06:19 GMT

Which modem firmware version are you running?

RE: subscribing in Assert tracker v2

Markus Tacker (he/him) — Thu, 23 Sep 2021 14:50:31 GMT

Hei, thanks for the trance. It was in parts corrupted, maybe due to UART issues, but I'll forward it internally for some analysis.

RE: subscribing in Assert tracker v2

Mustafa — Thu, 23 Sep 2021 06:16:30 GMT

Hello Markus,

I use iBasis sim in the Netherlands

the log file and modem trace are here below. Thanks

[00:00:00.658,325] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTING[0m
[00:00:02.131,439] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
[00:00:02.138,977] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
[00:00:03.256,195] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
[00:00:03.266,052] [0m<inf> event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
[00:00:03.283,081] [0m<dbg> cloud_module.state_set: State transition STATE_LTE_DISCONNECTED --> STATE_LTE_CONNECTED[0m
[00:00:03.294,158] [0m<dbg> cloud_module.connect_cloud: Connecting to cloud[0m
[00:00:03.301,635] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
[00:00:03.310,485] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
[00:00:03.320,190] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_CONNECTING[0m
[00:00:03.329,284] [0m<dbg> cloud_module.cloud_wrap_event_handler: CLOUD_WRAP_EVT_CONNECTING[0m
[00:00:03.338,378] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
[00:00:06.242,431] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_CONNECTED[0m
[00:00:06.415,985] [0m<dbg> aws_iot_integration.aws_iot_event_handler: AWS_IOT_EVT_READY[0m
[00:00:06.428,894] [0m<dbg> cloud_module.cloud_wrap_event_handler: CLOUD_WRAP_EVT_CONNECTED[0m
[00:00:06.438,568] [0m<inf> event_manager: CLOUD_EVT_CONNECTED[0m
[00:00:06.446,502] [0m<dbg> cloud_module.sub_state_set: Sub state transition SUB_STATE_CLOUD_DISCONNECTED --> SUB_STATE_CLOUD_CONNECTED[0m
[00:00:06.592,346] [0m<inf> event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
[00:00:06.611,938] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS, MOD_STAT)[0m
[00:00:06.642,974] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
[00:00:06.649,078] [0m<dbg> gps_module.sub_state_set: Sub state transition SUB_STATE_IDLE --> SUB_STATE_SEARCH[0m
[00:00:06.660,400] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_SEARCH_STARTED[0m
[00:00:06.668,457] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_AGPS_DATA_NEEDED[0m
[00:00:06.676,666] [0m<inf> event_manager: GPS_EVT_AGPS_NEEDED[0m
[00:00:06.683,532] [0m<dbg> sensor_module.environmental_data_get: No external sensors, submitting dummy sensor data[0m
[00:00:06.697,967] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
[00:00:06.706,390] [0m<inf> agps: SUPL is initialized[0m
[00:00:06.803,039] [0m<inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY[0m
[00:00:06.897,521] [0m<inf> agps: Starting SUPL session[0m
[00:00:06.934,448] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
[00:00:06.945,373] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_modem_dynamic_buffer: Entry: 1 of 2 in dynamic modem buffer filled[0m
[00:00:07.071,136] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
[00:00:07.204,376] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_bat_buffer: Entry: 1 of 2 in battery buffer filled[0m
[00:00:07.646,820] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_BLOCKED[0m
[00:00:09.066,253] [0m<inf> agps: SUPL session finished successfully[0m
[00:00:21.420,227] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_OPERATION_UNBLOCKED[0m
[00:01:00.363,952] [0m<inf> event_manager: APP_EVT_ACTIVITY_DETECTION_ENABLE[0m
[00:01:21.706,359] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
[00:01:21.780,334] [0m<inf> event_manager: DATA_EVT_DATA_SEND[0m
[00:01:21.787,261] [0m<dbg> cloud_codec.cloud_codec_encode_batch_data: No data to encode, JSON string empty...[0m
[00:01:21.834,259] [1;33m<wrn> cloud_module:  Data sent, data pointer: 0x200201f8[0m
[00:01:21.912,475] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:01:25.534,332] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_SEARCH_TIMEOUT[0m
[00:01:25.542,358] [0m<inf> event_manager: GPS_EVT_TIMEOUT[0m
[00:01:25.548,614] [0m<inf> event_manager: GPS_EVT_INACTIVE[0m
[00:01:25.554,901] [0m<dbg> gps_module.sub_state_set: Sub state transition SUB_STATE_SEARCH --> SUB_STATE_IDLE[0m
[00:01:25.565,704] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
[00:01:25.572,723] [0m<dbg> cloud_codec.cloud_codec_encode_data: No data to encode, JSON string empty...[0m
[00:10:00.363,952] [0m<inf> event_manager: APP_EVT_DATA_GET_ALL[0m
[00:10:00.370,910] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS)[0m
[00:10:00.441,284] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
[00:10:00.447,418] [0m<dbg> gps_module.sub_state_set: Sub state transition SUB_STATE_IDLE --> SUB_STATE_SEARCH[0m
[00:10:00.458,312] [0m<dbg> sensor_module.environmental_data_get: No external sensors, submitting dummy sensor data[0m
[00:10:00.489,593] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
[00:10:00.545,013] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
[00:10:00.599,121] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
[00:10:00.606,811] [0m<dbg> cloud_codec_ringbuffer.cloud_codec_populate_bat_buffer: Entry: 2 of 2 in battery buffer filled[0m
[00:11:04.505,828] [0m<dbg> gps_module.gps_event_handler: GPS_EVT_SEARCH_TIMEOUT[0m
[00:11:04.513,885] [0m<inf> event_manager: GPS_EVT_TIMEOUT[0m
[00:11:04.520,141] [0m<inf> event_manager: GPS_EVT_INACTIVE[0m
[00:11:04.526,458] [0m<dbg> gps_module.sub_state_set: Sub state transition SUB_STATE_SEARCH --> SUB_STATE_IDLE[0m
[00:11:04.537,261] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
[00:11:04.561,706] [0m<inf> event_manager: DATA_EVT_DATA_SEND[0m
[00:11:04.568,664] [0m<dbg> cloud_codec.cloud_codec_encode_batch_data: No data to encode, JSON string empty...[0m
[00:11:04.615,417] [1;33m<wrn> cloud_module:  Data sent, data pointer: 0x2001fc98[0m
[00:11:04.665,466] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
[00:11:05.086,456] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
[00:11:32.287,109] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_09_2D00_23T05_2D00_57_2D00_18.559Z.rar

RE: subscribing in Assert tracker v2

Markus Tacker (he/him) — Wed, 22 Sep 2021 13:54:29 GMT

Not really sure what is causing this with the limited information at hand.

If the device is not disconnected from the broker when it sends PINGREQs after keep alive > 130 secs, it indicates that the NAT rule and TLS session are at least alive.
However some networks even drop TCP packets silently.

It would be great if you could provide more details:

What SIM are you using?
Which network?
Please provide logs from the application,
and ideally a modem trace.