No Custom Parameters
Rejects an incoming call, indicating to the remote endpoint that the called party is not able to receive this call.
When a call is inbound to an script via
IncomingCall, the call is in a ringing state and a script can choose to do one of 5 things:
AcceptCall, or simply do nothing with the call. The practical use of
Reject is to indicate to the calling party that their call could not be completed.
From the perspective of the script instance initiated by the incoming call, the telephony protocol of the call has already been chosen by the time
IncomingCall has been fired. However, any call created by the application via
Barge will use the protocol configured on the partition of the script instance. See Call Routing for more information on how the application server interfaces with the outside world for the routing of calls.
The Call Control API makes every effort to abstract the complexities of the underlying telephony protocol; however, one should consult the Call Control Feature Matrix to understand what Call Control actions and action parameters are valid for each of the four supported protocols. One can set installation and deployment guidelines based on the Call Control actions and action parameters that an application uses; the Call Control Feature Matrix makes developing such guidelines feasible.
|Parameter Name||.NET Type||Default||Description|
|CallId *||Indicates the call to reject with |
No Result Data