Triggering
JTapiCallInitiated indicates that a line on a monitored device has gone off-hook.
A phone going off-hook does not correlate to a phone call. If building an application that is concerned foremost with knowing a phone has made a call, then consider using the JTapiCallEstablished event instead for the basis of your script trigger.
Subsequent events indicate important state changes of the call. JTapiCallActive indicates that the call has been answered by the remote party. JTapiHangup indicates that call has been gone on-hook if JTapiCallActive
has not yet occurred.
The term 'CallInitiated' is a very strict interpretation of a JTAPI call; when a phone is taken off-hook, a new call is created within Cisco Unified Communications Manager, although there is not yet a remote number dialed by the phone device. Therefore, there is no To parameter associated with this event.
| Parameter Name | .NET Type | Description |
|---|---|---|
| CallControlCause | System.String | The JTAPI protocol CallControlCause for the call. Please refer to the JTAPI documentation for the complete list of Cause and CallControlCause reasons. |
| From | System.String | The line number on the device that has gone off-hook. |
| JTapiCallId | System.String | The JTapi internal call Id. This can be used to co-relate the originating and the terminating ends of the call. |
| StackToken | System.String | The JTAPI protocol call ID. |
| CallId | System.Int64 | Unique identifier used to identify this call leg in all subsequent 3rd-Party JTAPI API operations, such as JTapiRejectCall, JTapiAnswerCall, JTapiRedirect. |
| DeviceName | System.String | The name of the device that has gone off-hook. |