JTapiHangupCall indicates that a call on a monitored device has ended. This is used by the Etch applications and will not appear in the list of events in the designer. The legacy applications will continue to get the JTapiHangup event.
JTapiHangupCall 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.
|Parameter Name||.NET Type||Description|
|Cause||The JTAPI protocol cause for the call ending. Please refer to the JTAPI documentation for the complete list of Cause and CallControlCause end reasons.|
|DeviceName||The name of the device that has the ended call.|
|JTapiCallId||The JTapi internal call Id. This can be used to co-relate the originating and the terminating ends of the call.|
|CallControlCause||The JTAPI protocol CallControlCause for the call ending. Please refer to the JTAPI documentation for the complete list of Cause and CallControlCause end reasons.|
|StackToken||The JTAPI protocol call ID.|
|CallId||Unique identifier used to identify which call has ended.|