- After receiving an ADIEVN_INCOMING_CALL event, the application must invoke either adiAnswerCall or adiRejectCall.
- adiRejectCall
causes the trunk protocol to reject the incoming call and, depending upon the method argument, perform one of the following actions:
- The generated reject tone is played until the remote party disconnects.
- If the method is ADI_REJ_USER_AUDIO, then the application can generate any programmable tone and perform voice playback functions. For example, you could generate an SIT (Special Information Tone) message. The application must wait for the ADIEVN_REJECTING_CALL event before generating an SIT.
- If the remote party disconnects while the application rejects the call, the ADI service will only generate an ADIEVN_CALL_DISCONNECTED event. In this case, no ADIEVN_REJECTING_CALL event is delivered.
- Some protocols allow you to use adiSetExtendedArgs to set additional arguments to adiRejectCall. For more information about controlling calls under specific TCPs, refer to the AG CAS for ADI Service Installation and Developer's Manual.
Note: This function is not available when using the NOCC protocol.
(Page 30 of 69 in this chapter) Version