Triggering
JTapiIncomingCall indicates that a call has been routed to a line on a monitored device and is currently ringing and unanswered.
When a call is inbound to an script via JTapiIncomingCall, the call is in a ringing state and a script can choose to do one of 4 things: JTapiRejectCall, JTapiAnswerCall, JTapiRedirect, or simply do nothing with the call.
The JTapiHangup event can occur after JTapiIncomingCall, 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.
None.
| Parameter Name | .NET Type | Description |
|---|---|---|
| StackToken | System.String | The JTAPI protocol call ID. |
| OriginalTo | System.String | The original number which was dialed.
This will be the same as the To field unless the call has been redirected, transferred, or translated while being routed. |
| CallId | System.Int64 | Unique identifier used to identify this call leg in all subsequent 3rd-Party JTAPI API operations, such as JTapiRejectCall, JTapiAnswerCall, or JTapiRedirect. |
| DeviceName | System.String | The name of the device that has received the call. |
| To | System.String | The called number for this call. This number may not correspond to the number the remote endpoint initially dialed. |
| From | System.String | The calling party number for this call. |