Q2686- client socket FCM issue

[awneil]

@aezakmi

can you tell any way to ensure the socket creation is success?That will help me a lot

WIP indicates state changes of the socket to you via the WIP_CEV_ events.

Look at the State Diagram given in the WIP User Guide.

in remote site who will reboot?.

Your application must include timeouts on all waits - and have appropriate recovery mechanisms on timeout (and other) errors.

really i can’t get why this is happening?

After wip_TCPClientCreate() you certainly should get either WIP_CEV_OPEN or WIP_CEV_ERROR - again, see that State Diagram given in the WIP User Guide.

Are you sure that you have a reliable bearer connection?

Can you connect reliably to the same host over GPRS from a PC?

WIP Debugging Tips:

wip_bearerOpen returning WIP_BERR_BAD_STATE

Here’s a debugging suggestion: Use the old TMT, and enable the ATI Level 1 Traces: [image] (you can probably also do this in M2MStudio - I just don’t know how) This will let you see the AT commands that WIP is using internally - and, most importantly, any error responses to those commands. Also be sure that you’ve enabled all the WIP traces - see: Multiple HTTP Requests - every other one fails You should also check precisely what return code you’re getting from wip_bearerStart - the ASSER…

forum.sierrawireless.com/viewtop … ces#p18469