No Custom Parameters
Redirects a call currently ringing on a monitored device to a new destination.
JTapiRedirect redirects a call inbound to a phone device, causing the call to be sent to a new destination elsewhere.
You can not successfully use
JTapiRedirect after the ringing device has been answered (most likely cause is the user answering the phone, but another JTAPI-based application could be the cause of the answer as well). You can know in your application that the call has already been answered if the
JTapiCallActive fires before you have used the
|Parameter Name||.NET Type||Default||Description|
|PrefferedOriginalCalledParty||The called party information that would appear in the redirect request.|
|To *||The destination number for the redirected 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.|
|CallId *||Indicates the call to redirect with |
No Result Data