Here is the context: Fastrack Supreme 20 with Firmware 22.214.171.124208311102 and Internet Library Package 126.96.36.199206250935.
I check the registration on the GMS network with +CREG with stat 1 (Home network) or 5 (Roaming).
Then I open and start a GPRS bearer and when the bearer is started, a TCP client is created with wip_TCPClientCreate.
I recently added the log of all GPRS events with adl_gprsSubscribe and I got some strange sequences.
Log are saved into flash memory and sent to a server when a new connection is available.
The time in the logs are the reception times on server side and the reception order on server side should be equal to the sending order.
Setup, Attach and Activate are the events I’m waiting for.
But I don’t understand why there is another ATTACH event.
In this sequence, there is an error on the TCP socket. So a reconnection is done (TCP socket is closed, GPRS bearer is stopped and closed, GPRS bearer is opened, started and a new TCP client is created). I will not detail but I use a state machine to call the right method at the right time. The reconnection is successful.
Here I don’t understand why the ATTACH is after the ACTIVATE_OK. From my knowledge on GPRS, the sequence order should be ATTACH then ACTIVATE.
And I don’t understand the second ATTACH event.
And I’m surprised to not have a DETACH event.
Any suggestion about these strange sequences ?
In previous log, I did not log the Context ID from GPRS Event handler.
I did a test with traces, Fastrack Supreme connected to my laptop and added the Cid into bracket.
Sequence is now:
So the new question is why I got a new Cid 5 ?
Another question: how to get more details on WIP_CERR_NETWORK_UNREACHABLE error ?
On the last 3 days, I get this error at the same time around 16:44.
The modem is online from 4:30 a.m. to 10:00 p.m.