IncomingCall indicates that a call has been received by the application server.
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.
RemoteHangup event can occur after
IncomingCall, even if the call has not been answered. In this case, just as when the call has been answered and is established, it indicates that the remote endpoint has terminated the call, and the call is over.
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||Description|
|CallId||Unique identifier used to identify this call leg in all subsequent Call Control API operations, such as |
|From||The calling party number for this call.|
|To||The called number for this call. This number may not correspond to the number the remote endpoint initially dialed.|
|OriginalTo||The original number which was dialed.
This will be the same as the |
|DisplayName||The caller's friendly name.|
|StackToken||The ID of the call used by underlying protocol stack|