6.4.8 IPCallControl::connected State

The application waits for a GCEV_DISCONNECTED or USR_DISCONNECT event. In the case of GCEV_DISCONNECTED, the application calls getResultValue( ) to get the disconnect reason and then calls dropCall( ). If the dropCall( ) function fails, the application calls resetLineDevice( ) to reset the line device and the state transitions to Init. Otherwise, the state transitions to Dropping.

In the case of USR_DISCONNECT, the application retrieves the DropReason from the EventData and calls dropCall( ). If the dropCall( ) function fails, the application calls resetLineDevice( ) to reset the line device and the state transitions to Init. Otherwise, the state transitions to Dropping.

If the application receives a GCEV_EXTENSION event, it calls getExtensionInfo( ) and remains in the Connected state.

If the application receives a USR_SEND_UII event, it calls sendUII( ) and remains in the Connected state.

If the application receives a USR_SEND_FACILITY event, it calls sendFacilityMessage( ) and remains in the Connected state.

If the application receives a USR_SEND_NS_COMMAND event, it calls sendNonstandardCommand( ) and remains in the Connected state.

If the application receives a GCEV_ALARM event, it calls printQoS( ) and remains in the Connected state.

Click here to contact Telecom Support Resources