I am using HTTPs stack to post data on the server using HE910-G module. Once data posting is done, we want to close socket immediately. but when we sent AT#SSLH=1,0 command to the module, it takes more than 100 seconds to return “OK” after that socket is closed.
Here i have mentioned below log along with time stamping for your reference. Please let us know what is the issue.
Hello, I suppose that the server is not responding to the FIN request and the module is waiting for the ACK to come back. In the default configuration the socket should be considered as closed after 10 seconds, but you have increased this timeout to 100 seconds with AT#SSLCFG, parameter <defTo>, so you have to wait at least 100 seconds, before the socket is considered as closed.
Dear Sir,
I am using HTTPs stack to post data on the server using HE910-G module. Once data posting is done, we want to close socket immediately. but when we sent AT#SSLH=1,0 command to the module, it takes more than 100 seconds to return “OK” after that socket is closed.
Here i have mentioned below log along with time stamping for your reference. Please let us know what is the issue.
23-11-2016 18:01:57.435 [TX] – at#sslcfg=1,1,1500,2000,1000,100,1,2,0,0
23-11-2016 18:01:57.453 [RX] –
OK
23-11-2016 18:01:59.872 [TX] – AT#SGACT=1,1
23-11-2016 18:01:59.889 [RX] –
+CME ERROR: context already activated
23-11-2016 18:02:03.449 [TX] – AT#SSLEN=1,1
23-11-2016 18:02:03.464 [RX] –
+CME ERROR: SSL already activated
23-11-2016 18:02:06.397 [TX] – AT#SSLSECCFG=1,0,0
23-11-2016 18:02:06.413 [RX] –
OK
23-11-2016 18:02:07.912 [TX] – AT#SSLD=1,443,”xxxxxxkerIOTHub.azure-devices.net”,0,1,2000
23-11-2016 18:02:12.419 [RX] –
OK
23-11-2016 18:02:13.388 [TX] – at#SSLSEND=1,2000
23-11-2016 18:02:13.403 [RX] –
>
23-11-2016 18:02:14.981 [TX] – POST /devices/DEV001/messages/events?api-version=2016-02-03 HTTP/1.1
23-11-2016 18:02:15.807 [TX] – Host: StrykerIOTHub.azure-devices.net
23-11-2016 18:02:16.603 [TX] – Content-type: application/json
23-11-2016 18:02:17.395 [TX] – Content-Length:179
23-11-2016 18:02:18.210 [TX] – Authorization:SharedAccessSignature sr=StrykerIOTHub.azure-devices.net&sig=6WfzUU1xvYAFJhvmNcsWhrmM%2bqFHwOL5gjeq%2byuzEsk%3d&se=1503565034&skn=iothubowner
23-11-2016 18:02:19.176 [TX] –
{“Device_Id”:”DEV001″,”Altitude”:”86.00100000″,”Longitude”:”76.7794000″,”Latitude”:”30.73330000″,”Current_Status”:”1″,”Battery_Status”:”3600″,”Temperature”:”23″,”Humidity”:”60″}
23-11-2016 18:02:20.935 [TX] – _
23-11-2016 18:02:20.952 [RX] –
OK
SSLSRING: 1,1
23-11-2016 18:02:22.317 [TX] – AT#SSLRECV=1,1000,2000
23-11-2016 18:02:22.343 [RX] –
#SSLRECV: 114
HTTP/1.1 204 No Content
Content-Length: 0
Server: Microsoft-HTTPAPI/2.0
Date: Wed, 23 Nov 2016 12:32:21 GMT
OK
23-11-2016 18:02:24.474 [TX] – AT#SSLH=1
23-11-2016 18:04:22.147 [RX] –
OK
Hello, I suppose that the server is not responding to the FIN request and the module is waiting for the ACK to come back.
In the default configuration the socket should be considered as closed after 10 seconds, but you have increased this timeout to 100 seconds with AT#SSLCFG, parameter <defTo>, so you have to wait at least 100 seconds, before the socket is considered as closed.