Azure-iot-sdk-c: Interfacing CAT-M modem to azure-iot-sdk-C

Created on 14 Sep 2020  路  18Comments  路  Source: Azure/azure-iot-sdk-c

Hi,

Greetings! We have a Gateway with yocto linux and CAT-M modem to connect to IoT hub. Running azure-iot-sdk-c to establish connection with IoTHub and push data. It appears connection is establish and sdk accepts data to send. However, it is unable to delivery the data, I get the following error.

Sep 11 16:03:33 imx6ul-var-dart AzureLink[744]: Error: Time:Fri Sep 11 16:03:33 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/saslclientio.c Func:saslclientio_send Line:1133 send called while not open
Sep 11 16:03:33 imx6ul-var-dart AzureLink[744]: Error: Time:Fri Sep 11 16:03:33 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/connection.c Func:on_bytes_encoded Line:241 Cannot send encoded bytes
Sep 11 16:03:33 imx6ul-var-dart AzureLink[744]: Error: Time:Fri Sep 11 16:03:33 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/saslclientio.c Func:saslclientio_close Line:1083 saslclientio_close called while not open
Sep 11 16:03:33 imx6ul-var-dart AzureLink[744]: Error: Time:Fri Sep 11 16:03:33 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/connection.c Func:on_bytes_encoded Line:245 xio_close failed
Sep 11 16:03:33 imx6ul-var-dart AzureLink[744]: Error: Time:Fri Sep 11 16:03:33 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/saslclientio.c Func:saslclientio_close Line:1083 saslclientio_close called while not open
Sep 11 16:03:33 imx6ul-var-dart AzureLink[744]: Error: Time:Fri Sep 11 16:03:33 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/connection.c Func:connection_close Line:1339 xio_close failed

Interestingly, if I replace the CAT-M modem with a CAT-1 modem. Same code, same unit and same everything, data gets through and no errors.

Difference: CAT-M uses cdc-wdm (MSM) interface and CAT1 uses ttyACMx (PPP) interface.

Could you help resolving the issue? Why interfacing with CAT-M modem gives above error?

Regards
Narendra Setty

question
Source
picture narendranaren14

All 18 comments

Hi @narendranaren14 ,
thanks for your question.

Is this all the log you got printed? Do you have entries printed before the output you pasted?

ewertons picture ewertons on 14 Sep 2020

Same question asked in Microsoft Q&A: https://docs.microsoft.com/en-us/answers/questions/94651/index.html

asergaz picture asergaz on 15 Sep 2020
👍1

Hi @ewertons,

More debug information.

Sep 15 15:35:10 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_connection.c Func:on_cbs_error Line:156 CBS Error occured
Sep 15 15:35:10 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c414d0
Sep 15 15:35:10 Controller AzureLink[13180]: 2020-09-15.15:35:10, Message confirmation, result = 3 (ERROR)
Sep 15 15:35:10 Controller AzureLink[13180]: , Bad CLIENT_CONFIRMATION
Sep 15 15:35:10 Controller AzureLink[13180]: Added to Retry Queue msghandle = 0x1c414d0
Sep 15 15:35:10 Controller AzureLink[13180]: PendingRetryQueue.size() after push(): 1
Sep 15 15:35:10 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c46028
Sep 15 15:35:10 Controller AzureLink[13180]: 2020-09-15.15:35:10, Message confirmation, result = 3 (ERROR)
Sep 15 15:35:10 Controller AzureLink[13180]: , Bad CLIENT_CONFIRMATION
Sep 15 15:35:10 Controller AzureLink[13180]: Added to Retry Queue msghandle = 0x1c46028
Sep 15 15:35:10 Controller AzureLink[13180]: PendingRetryQueue.size() after push(): 2
Sep 15 15:35:10 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c49578
Sep 15 15:35:10 Controller AzureLink[13180]: 2020-09-15.15:35:10, Message confirmation, result = 3 (ERROR)
Sep 15 15:35:10 Controller AzureLink[13180]: , Bad CLIENT_CONFIRMATION
Sep 15 15:35:10 Controller AzureLink[13180]: Added to Retry Queue msghandle = 0x1c49578
Sep 15 15:35:10 Controller AzureLink[13180]: PendingRetryQueue.size() after push(): 3
Sep 15 15:35:10 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_telemetry_messenger.c Func:process_state_changes Line:1512 messagesender reported unexpected state 4 while messenger was started
Sep 15 15:35:10 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_device.c Func:device_do_work Line:855 Device 'xxxx' is started but messenger reported unexpected state 4
Sep 15 15:35:10 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:10 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 5 (COMMUNICATION_ERROR)
Sep 15 15:35:10 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 6; number of previous failures: 0)
Sep 15 15:35:10 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:10 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:35:10 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/cbs.c Func:cbs_put_token_async Line:456 put token called while closed or in error
Sep 15 15:35:10 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:put_SAS_token_to_cbs Line:228 Failed putting SAS token to CBS for device 'xxxx' (cbs_put_token failed)
Sep 15 15:35:10 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:create_and_put_SAS_token_to_cbs Line:347 Failed putting SAS token to CBS
Sep 15 15:35:10 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:authentication_do_work Line:692 Failed authenticating device 'xxxx' using device keys
Sep 15 15:35:11 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:11 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 2 (BAD_CREDENTIAL)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 4; number of previous failures: 1)
Sep 15 15:35:11 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:11 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/cbs.c Func:cbs_put_token_async Line:456 put token called while closed or in error
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:put_SAS_token_to_cbs Line:228 Failed putting SAS token to CBS for device 'xxxx' (cbs_put_token failed)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:create_and_put_SAS_token_to_cbs Line:347 Failed putting SAS token to CBS
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:authentication_do_work Line:692 Failed authenticating device 'xxxx' using device keys
Sep 15 15:35:11 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:11 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 2 (BAD_CREDENTIAL)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 4; number of previous failures: 2)
Sep 15 15:35:11 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:11 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/cbs.c Func:cbs_put_token_async Line:456 put token called while closed or in error
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:put_SAS_token_to_cbs Line:228 Failed putting SAS token to CBS for device 'xxxx' (cbs_put_token failed)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:create_and_put_SAS_token_to_cbs Line:347 Failed putting SAS token to CBS
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:authentication_do_work Line:692 Failed authenticating device 'xxxx' using device keys
Sep 15 15:35:11 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:11 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 2 (BAD_CREDENTIAL)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 4; number of previous failures: 3)
Sep 15 15:35:11 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:11 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/cbs.c Func:cbs_put_token_async Line:456 put token called while closed or in error
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:put_SAS_token_to_cbs Line:228 Failed putting SAS token to CBS for device 'xxxx' (cbs_put_token failed)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:create_and_put_SAS_token_to_cbs Line:347 Failed putting SAS token to CBS
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:authentication_do_work Line:692 Failed authenticating device 'xxxx' using device keys
Sep 15 15:35:11 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:11 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 2 (BAD_CREDENTIAL)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 4; number of previous failures: 4)
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_DoWork Line:1415 Device 'xxxx' reported a critical failure; connection retry will be triggered.
Sep 15 15:35:11 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_CONNECTED to AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED
Sep 15 15:35:11 Controller AzureLink[13180]: Info: Preparing transport for re-connection
Sep 15 15:35:11 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:35:10 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:on_amqp_connection_state_changed Line:635 amqp_connection was closed unexpectedly; connection retry will be triggered.
Sep 15 15:35:11 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED to AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED
Sep 15 15:35:11 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED to AMQP_TRANSPORT_STATE_READY_FOR_RECONNECTION
Sep 15 15:35:11 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:11 Controller AzureLink[13180]: 2020-09-15.15:35:10, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:35:11 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_READY_FOR_RECONNECTION to AMQP_TRANSPORT_STATE_RECONNECTING
Sep 15 15:35:11 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_RECONNECTING to AMQP_TRANSPORT_STATE_CONNECTED
Sep 15 15:35:11 Controller AzureLink[13180]: No point retrying - there is no connectivity to Azure
Sep 15 15:35:12 Controller AzureLink[13180]: No point retrying - there is no connectivity to Azure
Sep 15 15:35:13 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:35:13 Controller AzureLink[13180]: 2020-09-15.15:35:13, Connection status, result = 0 (AUTHENTICATED), reason = 6 (OK)
Sep 15 15:35:13 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for REtransmission to IoT Hub, msghandle_toretry = 0x1c414d0
Sep 15 15:35:13 Controller AzureLink[13180]: PendingRetryQueue.size() after pop(): 2
Sep 15 15:35:14 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for REtransmission to IoT Hub, msghandle_toretry = 0x1c46028
Sep 15 15:35:14 Controller AzureLink[13180]: PendingRetryQueue.size() after pop(): 1
Sep 15 15:35:15 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for REtransmission to IoT Hub, msghandle_toretry = 0x1c49578
Sep 15 15:35:15 Controller AzureLink[13180]: PendingRetryQueue.size() after pop(): 0
Sep 15 15:39:14 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:39:14 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_connection.c Func:on_cbs_error Line:156 CBS Error occured
Sep 15 15:39:14 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:39:14 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:on_amqp_connection_state_changed Line:635 amqp_connection was closed unexpectedly; connection retry will be triggered.
Sep 15 15:39:14 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_CONNECTED to AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED
Sep 15 15:39:14 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c414d0
Sep 15 15:39:14 Controller AzureLink[13180]: 2020-09-15.15:39:14, Message confirmation, result = 3 (ERROR)
Sep 15 15:39:14 Controller AzureLink[13180]: , Bad CLIENT_CONFIRMATION
Sep 15 15:39:14 Controller AzureLink[13180]: Added to Retry Queue msghandle = 0x1c414d0
Sep 15 15:39:14 Controller AzureLink[13180]: PendingRetryQueue.size() after push(): 1
Sep 15 15:39:14 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c46028
Sep 15 15:39:14 Controller AzureLink[13180]: 2020-09-15.15:39:14, Message confirmation, result = 3 (ERROR)
Sep 15 15:39:14 Controller AzureLink[13180]: , Bad CLIENT_CONFIRMATION
Sep 15 15:39:14 Controller AzureLink[13180]: Added to Retry Queue msghandle = 0x1c46028
Sep 15 15:39:14 Controller AzureLink[13180]: PendingRetryQueue.size() after push(): 2
Sep 15 15:39:14 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c49578
Sep 15 15:39:14 Controller AzureLink[13180]: 2020-09-15.15:39:14, Message confirmation, result = 3 (ERROR)
Sep 15 15:39:14 Controller AzureLink[13180]: , Bad CLIENT_CONFIRMATION
Sep 15 15:39:14 Controller AzureLink[13180]: Added to Retry Queue msghandle = 0x1c49578
Sep 15 15:39:14 Controller AzureLink[13180]: PendingRetryQueue.size() after push(): 3
Sep 15 15:39:14 Controller AzureLink[13180]: Info: Preparing transport for re-connection
Sep 15 15:39:14 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:39:14 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/saslclientio.c Func:saslclientio_send Line:1133 send called while not open
Sep 15 15:39:14 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:39:14 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/connection.c Func:on_bytes_encoded Line:241 Cannot send encoded bytes
Sep 15 15:39:14 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:39:14 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/saslclientio.c Func:saslclientio_close Line:1083 saslclientio_close called while not open
Sep 15 15:39:14 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:39:14 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/connection.c Func:on_bytes_encoded Line:245 xio_close failed
Sep 15 15:39:14 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:39:14 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/saslclientio.c Func:saslclientio_close Line:1083 saslclientio_close called while not open
Sep 15 15:39:14 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:39:14 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/connection.c Func:connection_close Line:1339 xio_close failed
Sep 15 15:39:14 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED to AMQP_TRANSPORT_STATE_READY_FOR_RECONNECTION
Sep 15 15:39:14 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:39:14 Controller AzureLink[13180]: 2020-09-15.15:39:14, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:39:14 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_READY_FOR_RECONNECTION to AMQP_TRANSPORT_STATE_RECONNECTING
Sep 15 15:39:14 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_RECONNECTING to AMQP_TRANSPORT_STATE_CONNECTED
Sep 15 15:39:14 Controller AzureLink[13180]: No point retrying - there is no connectivity to Azure
Sep 15 15:39:14 Controller AzureLink[13180]: Sending heartbeat to test connectivity to Azure
Sep 15 15:39:14 Controller AzureLink[13180]: FinalizeMsg - attached message properties.
Sep 15 15:39:14 Controller AzureLink[13180]: Message properties are:
Sep 15 15:39:14 Controller AzureLink[13180]: DataSource => App
Sep 15 15:39:14 Controller AzureLink[13180]: MessageType => LinkHeartbeat
Sep 15 15:39:14 Controller AzureLink[13180]: TelemetryForm => Hbeat
Sep 15 15:39:14 Controller AzureLink[13180]: Tue Sep 15 15:39:14 2020
Sep 15 15:39:14 Controller AzureLink[13180]: Message (LinkHeartbeat) (AVRO) (397) SENT
Sep 15 15:39:15 Controller AzureLink[13180]: !!!!!! GenerateUUID - 36646c06-7344-415f-94cf-0bd62610f4b1
Sep 15 15:39:15 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for transmission to IoT Hub, msghandle = 0x1c41780
Sep 15 15:39:15 Controller AzureLink[13180]: No point retrying - there is no connectivity to Azure
Sep 15 15:39:16 Controller AzureLink[13180]: No point retrying - there is no connectivity to Azure
Sep 15 15:39:16 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:39:16 Controller AzureLink[13180]: 2020-09-15.15:39:16, Connection status, result = 0 (AUTHENTICATED), reason = 6 (OK)
Sep 15 15:39:17 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c41780
Sep 15 15:39:17 Controller AzureLink[13180]: 2020-09-15.15:39:17, Message confirmation, result = 0 (OK)
Sep 15 15:39:17 Controller AzureLink[13180]: DEBUG: This is a Hbeat message!!!
Sep 15 15:39:17 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for REtransmission to IoT Hub, msghandle_toretry = 0x1c414d0
Sep 15 15:39:17 Controller AzureLink[13180]: PendingRetryQueue.size() after pop(): 2
Sep 15 15:39:18 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for REtransmission to IoT Hub, msghandle_toretry = 0x1c46028
Sep 15 15:39:18 Controller AzureLink[13180]: PendingRetryQueue.size() after pop(): 1
Sep 15 15:39:19 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for REtransmission to IoT Hub, msghandle_toretry = 0x1c49578
Sep 15 15:39:19 Controller AzureLink[13180]: PendingRetryQueue.size() after pop(): 0
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_connection.c Func:on_cbs_error Line:156 CBS Error occured
Sep 15 15:43:18 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c414d0
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Message confirmation, result = 3 (ERROR)
Sep 15 15:43:18 Controller AzureLink[13180]: , Bad CLIENT_CONFIRMATION
Sep 15 15:43:18 Controller AzureLink[13180]: Added to Retry Queue msghandle = 0x1c414d0
Sep 15 15:43:18 Controller AzureLink[13180]: PendingRetryQueue.size() after push(): 1
Sep 15 15:43:18 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c46028
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Message confirmation, result = 3 (ERROR)
Sep 15 15:43:18 Controller AzureLink[13180]: , Bad CLIENT_CONFIRMATION
Sep 15 15:43:18 Controller AzureLink[13180]: Added to Retry Queue msghandle = 0x1c46028
Sep 15 15:43:18 Controller AzureLink[13180]: PendingRetryQueue.size() after push(): 2
Sep 15 15:43:18 Controller AzureLink[13180]: sendConfirmationCallback: message msghandle = 0x1c49578
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Message confirmation, result = 3 (ERROR)
Sep 15 15:43:18 Controller AzureLink[13180]: , Bad CLIENT_CONFIRMATION
Sep 15 15:43:18 Controller AzureLink[13180]: Added to Retry Queue msghandle = 0x1c49578
Sep 15 15:43:18 Controller AzureLink[13180]: PendingRetryQueue.size() after push(): 3
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_telemetry_messenger.c Func:process_state_changes Line:1512 messagesender reported unexpected state 4 while messenger was started
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_device.c Func:device_do_work Line:855 Device 'xxxx' is started but messenger reported unexpected state 4
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 5 (COMMUNICATION_ERROR)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 6; number of previous failures: 0)
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/cbs.c Func:cbs_put_token_async Line:456 put token called while closed or in error
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:put_SAS_token_to_cbs Line:228 Failed putting SAS token to CBS for device 'xxxx' (cbs_put_token failed)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:create_and_put_SAS_token_to_cbs Line:347 Failed putting SAS token to CBS
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:authentication_do_work Line:692 Failed authenticating device 'xxxx' using device keys
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 2 (BAD_CREDENTIAL)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 4; number of previous failures: 1)
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/cbs.c Func:cbs_put_token_async Line:456 put token called while closed or in error
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:put_SAS_token_to_cbs Line:228 Failed putting SAS token to CBS for device 'xxxx' (cbs_put_token failed)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:create_and_put_SAS_token_to_cbs Line:347 Failed putting SAS token to CBS
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:authentication_do_work Line:692 Failed authenticating device 'xxxx' using device keys
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 2 (BAD_CREDENTIAL)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 4; number of previous failures: 2)
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/cbs.c Func:cbs_put_token_async Line:456 put token called while closed or in error
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:put_SAS_token_to_cbs Line:228 Failed putting SAS token to CBS for device 'xxxx' (cbs_put_token failed)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:create_and_put_SAS_token_to_cbs Line:347 Failed putting SAS token to CBS
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:authentication_do_work Line:692 Failed authenticating device 'xxxx' using device keys
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 2 (BAD_CREDENTIAL)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 4; number of previous failures: 3)
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/uamqp/src/cbs.c Func:cbs_put_token_async Line:456 put token called while closed or in error
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:put_SAS_token_to_cbs Line:228 Failed putting SAS token to CBS for device 'xxxx' (cbs_put_token failed)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:create_and_put_SAS_token_to_cbs Line:347 Failed putting SAS token to CBS
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:authentication_do_work Line:692 Failed authenticating device 'xxxx' using device keys
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 2 (BAD_CREDENTIAL)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Device_DoWork Line:996 Failed performing DoWork for device 'xxxx' (device reported state 4; number of previous failures: 4)
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_DoWork Line:1415 Device 'xxxx' reported a critical failure; connection retry will be triggered.
Sep 15 15:43:18 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_CONNECTED to AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED
Sep 15 15:43:18 Controller AzureLink[13180]: Info: Preparing transport for re-connection
Sep 15 15:43:18 Controller AzureLink[13180]: Error: Time:Tue Sep 15 15:43:18 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:on_amqp_connection_state_changed Line:635 amqp_connection was closed unexpectedly; connection retry will be triggered.
Sep 15 15:43:18 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED to AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED
Sep 15 15:43:18 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_RECONNECTION_REQUIRED to AMQP_TRANSPORT_STATE_READY_FOR_RECONNECTION
Sep 15 15:43:18 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:18 Controller AzureLink[13180]: 2020-09-15.15:43:18, Connection status, result = 1 (UNAUTHENTICATED), reason = 6 (OK)
Sep 15 15:43:18 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_READY_FOR_RECONNECTION to AMQP_TRANSPORT_STATE_RECONNECTING
Sep 15 15:43:18 Controller AzureLink[13180]: Info: Transport state changed from AMQP_TRANSPORT_STATE_RECONNECTING to AMQP_TRANSPORT_STATE_CONNECTED
Sep 15 15:43:18 Controller AzureLink[13180]: No point retrying - there is no connectivity to Azure
Sep 15 15:43:19 Controller AzureLink[13180]: No point retrying - there is no connectivity to Azure
Sep 15 15:43:20 Controller AzureLink[13180]: No point retrying - there is no connectivity to Azure
Sep 15 15:43:21 Controller AzureLink[13180]: connectionStatusCallback!
Sep 15 15:43:21 Controller AzureLink[13180]: 2020-09-15.15:43:21, Connection status, result = 0 (AUTHENTICATED), reason = 6 (OK)
Sep 15 15:43:21 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for REtransmission to IoT Hub, msghandle_toretry = 0x1c414d0
Sep 15 15:43:21 Controller AzureLink[13180]: PendingRetryQueue.size() after pop(): 2
Sep 15 15:43:22 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for REtransmission to IoT Hub, msghandle_toretry = 0x1c46028
Sep 15 15:43:22 Controller AzureLink[13180]: PendingRetryQueue.size() after pop(): 1
Sep 15 15:43:23 Controller AzureLink[13180]: IotHubClient_SendEventAsync accepted data for REtransmission to IoT Hub, msghandle_toretry = 0x1c49578
Sep 15 15:43:23 Controller AzureLink[13180]: PendingRetryQueue.size() after pop(): 0

Regards
Narendra Setty

narendranaren14 picture narendranaren14 on 15 Sep 2020

Thanks @narendranaren14 .
At no point I see in the logs above the SDK having any traffic actually sent or received to/from the Azure IoT Hub.
I still believe there is part of the log that is missing from the beginning, which would have some more details (perhaps from the TLS/socket layer).
Can you verify if the device actually has connectivity with the internet? It should be able to reach your IoT Hub at port 5671 (if using AMQP) or 8883 (if using MQTTT).

ewertons picture ewertons on 17 Sep 2020

Hi @ewertons,

The device has internet connectivity, I am able to ping. I have attached fresh log for your reference which has debug info from the beginning of the application.
CATMAzureLinkV2.log

Regards
Narendra Setty

narendranaren14 picture narendranaren14 on 17 Sep 2020

Thanks for the logs, @narendranaren14 .
At the beginning the client prints:
Sep 17 18:49:11 Controller AzureLink[11407]: Error: Time:Thu Sep 17 18:49:11 2020 File:/usr/src/debug/azure-iot-sdk-c/1.1.19-r0/azure-iot-sdk-c/c-utility/adapters/socketio_berkeley.c Func:signal_callback Line:242 Socket received signal 13.
Which is a broken pipe signal.
That is caused usually when the remote endpoint terminates the connection.
It could be caused by either bad credentials (wrong iothub fqdn, device id/sas token) or you are not providing the trusted cert for validating the TLS connection.

Could you verify if you have all of these set properly?
Also, just to confirm, what kind of authentication are you using? device keys, sas token or x509 certs?

ewertons picture ewertons on 18 Sep 2020

@ewertons

Thanks for the response! As I mentioned before, if I replace CAT-M with CAT-1. Everything exactly same, I am able to send the data to the cloud. There are no errors, once again everything is same (SIM, APN, and application). Yes, I have correct iothub fqdn. I am able to connect using CAT-1 modem, it is trusted cert.

We use symmetric key.

narendranaren14 picture narendranaren14 on 21 Sep 2020

@narendranaren14 ,
thanks for confirming.
Unfortunately this issue would be related to the layers below the Azure IoT SDK.
Still trying to help you here, are there any logs you can get from the system (yocto system logs) or the modem itself that could help you debug this issue? Have you tried looking into those logs?
Since the connection with the IoT Hub is terminated right away, there wouldn't be any logs in the Azure IoT service itself to help point what could be wrong.

ewertons picture ewertons on 22 Sep 2020

@ewertons
I have looked into syslog, there is nothing indicating an issue. I don't think I will be able to get modem logs. We don't have tools to capture modem logs (we are consumers).

Do you have any specific log in mind? Could you elaborate what do you mean for layers below IoT SDK? I can take a look at them.

narendranaren14 picture narendranaren14 on 23 Sep 2020

Hmm, I see. Yes, not having access to the modem logs will make it hard to debug.
By layers below the Azure IoT SDK I mean the TLS API (probably you are using openssl?) and socket API. If there are any errors on those layers and nothing is returned to the IoT SDK client (through error codes), there is no way the SDK can handle such failures.
Being frank, asking for your iothub fqdn would probably not work since there might be no traces in the Azure IoT HUB for this failure.
One course of action we usually have is to get a network traffic capture (with wireshark, e.g.) to see if we can find more information about what went wrong. Such capture would need to be obtained from the beginning of the process run, so all traces from the socket and TLS connections are saved.
So we have two actions here:

  1. Double check if you can access your modem logs and search for errors;
  2. Capture a network session trace with wireshark and share with us (opening an exception, please send to [email protected]). I will help you investigate that.
ewertons picture ewertons on 24 Sep 2020

@ewertons
Thanks! I will try to see if we can obtain modem logs. I will work on capture a network trace with wireshark and share it with you.

narendranaren14 picture narendranaren14 on 24 Sep 2020
👍1

My pleasure. I'm monitoring this ticket closely, I'll jump in as soon as I see an update.

ewertons picture ewertons on 24 Sep 2020

Hi @narendranaren14 ,
any update on this?

ewertons picture ewertons on 7 Oct 2020

Hi @narendranaren14 please share with us any update if you have, so we can continue with this issue open you confirm it is now resolved.
We will finally update the resolution in Microsoft Q&A as well. Thanks!

asergaz picture asergaz on 13 Oct 2020

Hi @narendranaren14 kind reminder for your follow-up. Thanks

asergaz picture asergaz on 3 Nov 2020

Hi @asergaz ,

My apologizes, Just last week I was able to figure out the problem. There was an issue with MTU. Apparently, recommended MTU for CAT-M is 1420, changing the value fixed the problem. It is not an issue with C SDK.

@ewertons Thanks for help, I got tcpdump that helped me to figure out the issue.

Regards
Narendra Setty

narendranaren14 picture narendranaren14 on 3 Nov 2020
👍1

Thanks @narendranaren14 I have provided the same answer in Microsoft Q&A. Please mark the answer there. @ewertons this can now be closed.

asergaz picture asergaz on 3 Nov 2020

@narendranaren14, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey

az-iot-builder-01 picture az-iot-builder-01 on 3 Nov 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

alexeystrakh picture alexeystrakh  路  5Comments
thematrix9 picture thematrix9  路  4Comments
vpetrigo picture vpetrigo  路  6Comments
kiranpradeep picture kiranpradeep  路  5Comments
Anil-Poolayulla-Chelottillam picture Anil-Poolayulla-Chelottillam  路  7Comments