2.2. gc_AnswerCall( )

The gc_AnswerCall( ) function must be used to complete the call establishment process:

• in asynchronous mode, this function can be called any time after a GCEV_OFFERED, GCEV_ACCEPT or a GCEV_PROGRESSING event is received.
• in synchronous mode, this function can be called any time after the successful completion of a gc_WaitCall( ) function.

This function sends a Connect message to the network to indicate that the call was accepted.

When using Springware boards, in the case of a DISCONNECT collision, if the inbound call is disconnected while the application was trying to answer the call, depending on the timing, the application may receive a GCEV_TASKFAIL event with the error code 0x10f (BADSTATE). The application should restart the timeslot using the gc_ResetLineDev( ) to handle this glare condition.

When using DM3 boards, in the case of a DISCONNECT collision, if the inbound call is disconnected while the application was trying to answer the call, the application receives a GCEV_DISCONNECTED event (no GCEV_TASKFAIL event is received). When using DM3 boards, the GCEV_DISCONNECTED event is a valid termination event for the gc_Answer( ) function.

For ISDN, the rings parameter is ignored. Instead, the default value is used.

Click here to contact Telecom Support Resources