# Handling WIP\_CSTATE\_BUSY

**URL:** <https://forum.sierrawireless.com/t/handling-wip-cstate-busy/5258>\
**Category:** Open AT\
**Created:** [September 20, 2011, 4:35pm UTC](https://forum.sierrawireless.com/t/handling-wip-cstate-busy/5258 "2011-09-20T16:35:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhallett](https://avatars.discourse-cdn.com/v4/letter/b/ed8c4c/32.png) [@bhallett](https://forum.sierrawireless.com/u/bhallett)\
**Post date:** [September 20, 2011, 4:35pm UTC](https://forum.sierrawireless.com/t/handling-wip-cstate-busy/5258/1 "2011-09-20T16:35:15Z")

</div>

Hello all,

First of all can anyone clarify what the state WIP\_CSTATE\_BUSY obtained from the WIPfunction wip\_getState  
actually refers to. The only comment I can find in the documentation is the comment:

“some configuration is happening, eventually the state will become READY”

- What does eventually actually mean/depend on?
- Is it telling me that configuration is taking place on a GSM, GPRS or TCP level?
- What is the best way to handle this state?

The reason for asking the best way to handle it is because I find that when the device attempts to connect (using wip\_TCPClientCreateOpts) and I get this state I find that it can remain in this state for an undesirable amount of time. Even after repeated (timed) reconnection attempts.

Regards

Barry

Any information would be greatfully received

---

<div class="post-metadata">

**Author:** ![Rex\_alex](https://avatars.discourse-cdn.com/v4/letter/r/73ab20/32.png) [@Rex\_alex](https://forum.sierrawireless.com/u/Rex_alex)\
**Post date:** [November 16, 2011, 10:39am UTC](https://forum.sierrawireless.com/t/handling-wip-cstate-busy/5258/2 "2011-11-16T10:39:06Z")

</div>

Hi,

Are you trying to handle the WIP\_CEV\_ERROR ? Because ,if the socket is not reachable, you would receive WIP\_CEV\_ERROR after the timeout which is typically 10 mins.  
If the error event is handled correctly, the exact reason for the failure  
in connection can be found out.

---

<div class="post-metadata">

**Author:** ![tomridl](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/tomridl/32/2704_2.png) [@tomridl](https://forum.sierrawireless.com/u/tomridl)\
**Post date:** [November 16, 2011, 11:21am UTC](https://forum.sierrawireless.com/t/handling-wip-cstate-busy/5258/3 "2011-11-16T11:21:46Z")

</div>

> [@bhallett](#):
>
> The reason for asking the best way to handle it is because I find that when the device attempts to connect (using wip\_TCPClientCreateOpts) and I get this state I find that it can remain in this state for an undesirable amount of time. Even after repeated (timed) reconnection attempts.

I have been having this exact same problem today, although it is intermittant. If anyone can shed some light on it that woulf be great.