No Custom Parameters
Causes a monitored device to place a call from a specific line.
JTapiMakeCall will cause a line on a monitored device to place a call.
JTapiCallActive event will fire to the same script that issued the
JTapiMakeCall, if the remote party specified by the
To action parameter answers the call.
If the remote party specified by the
To action parameter answers the call, then the call is bound to this script, meaning
JTapiHangup event will fire to the same script that issued the
If the outbound call from the monitored phone is cancelled before the remote party answers, then a
JTapiHangup event is sent to the same script that issued the
A device in Cisco Unified Communications Manager does not make or receive calls; the line(s) on that device do. Therefore it is necessary to specify a real line number found on the device as the value of the
From action parameter.
|Parameter Name||.NET Type||Default||Description|
|To *||The destination number for this call. In practice, this number must be routable according to the dial plan of the Cisco Unified Communications Manager cluster that the call is sent to.|
|DeviceName *||The name of a controlled device from which to place the call. The |
|From||The line on the controlled device from which to originate the call leg.|
|Parameter Name||.NET Type||Description|
|CallId||Unique identifier used to identify this call in all subsequent JTapi API operations.|