- After the ADIEVN_INCOMING_CALL event is delivered, the application must invoke either adiAnswerCall or adiRejectCall. adiAnswerCall answers an incoming call after the specified number of rings. ringcount specifies the total number of rings permitted before the application takes action.
- The ringcount action performed by adiAnswerCall is protocol-specific. For example, in the loop start protocol, ringcount indicates the number of rings to be detected before answering. In the DID protocol, ringcount indicates the number of rings played to the caller before answering.
- adiAnswerCall may be invoked multiple times as long as the specified CTA context's call control state is ADI_CC_STATE_INCOMING or ADI_CC_STATE_ANSWERING. The ringcount supplied with the most recent invocation of adiAnswerCall overrides any previous value.
- For example, if adiAnswerCall is invoked with a ringcount of 100000, the line will ring for what seems forever, until the remote party disconnects. If adiAnswerCall
is invoked subsequently with a ringcount of 5, the line will be answered if the total ring count since the incoming call arrived is greater than or equal to 5. A zero ringcount forces an immediate answer.
- Some protocols allow you to use adiSetExtendedArgs to set additional arguments to adiAnswerCall. For more information about controlling calls under specific TCPs, refer to the AG CAS for ADI Service Installation and Developer's Manual. Note that this function is not available when using the NOCC.
(Page 4 of 69 in this chapter) Version