Non-Triggering
JTapiHangup indicates that a call on a monitored device has ended.
JTapiHangup can be caused at various stages of a call. For instance, if the only event to have occured is JTapiCallInitiated in your script, then the line has gone on-hook. If the only event to have occurred is JTapiCallEstablished in your script, then the ringing call has been aborted. Finally, if the call has previously become active (indicated by JTapiCallActive), then one of the two parties in the call has hung up and the call is over.
None.
| Parameter Name | .NET Type | Description |
|---|---|---|
| Cause | System.String | The JTAPI protocol cause for the call ending. Please refer to the JTAPI documentation for the complete list of Cause and CallControlCause end reasons. |
| CallControlCause | System.String | The JTAPI protocol CallControlCause for the call ending. Please refer to the JTAPI documentation for the complete list of Cause and CallControlCause end reasons. |
| CallId | System.Int64 | Unique identifier used to identify which call has ended. |
| DeviceName | System.String | The name of the device that has the ended call. |
| StackToken | System.String | The JTAPI protocol call ID. |
| JTapiCallId | System.String | The JTapi internal call Id. This can be used to co-relate the originating and the terminating ends of the call. |