The connected call state

In the connected call state, a connection exists between the calling parties. The application can now invoke other telephony services suitable for completing its tasks (for example, DTMF, MF, playing/recording) until a disconnect occurs. The application can also transfer the call as described in Transferring calls.

The call reaches the connected call state when one of the following occurs:

When the call reaches the connected call state, NCCEVN_CALL_CONNECTED is returned to the application. The event value field contains the reason for connection. The call remains in this state until the application calls a function that changes the state, or receives an event indicating a state change.

The application can receive NCCEVN_BILLING_INDICATION while in the connected call state. This event indicates that a billing indication has arrived. Depending upon the protocol, this indication can be a billing pulse or some more complex indication such as ISDN or SS7. In some cases, the value field of this event contains the billing units charged. No state transition occurs with this event. The application can call nccQueryCapability to determine if the protocol supports billing indications.

The NCC.START.eventmask bit controls whether two other events appear during the connected call state. These events are only relevant if the call is outbound, the NCC_CON_ON_CALL_PROCEEDING bit is set in the NCC_PLACECALL_PARMS connectmask passed with nccPlaceCall, and the remote end has not yet answered:

Event

Description

NCCEVN_REMOTE_ALERTING

Indicates that the remote end is ringing. Does not cause a state transition.

NCCEVN_REMOTE_ANSWERED

Generated at the first positive indication that the remote party has answered; for example, out-of-band signaling, voice, or modem tone. The event value field contains the indication type. No state transition occurs.

For more information, refer to NCC API global parameters.