Platform SDK: TAPI |
Session redirection allows an application to deflect an offered session to another address without answering the call. The application can do redirection on a call-by-call basis. For example, an application might allow a user to specify different redirections based on caller ID information. After a call has been successfully redirected, the state typically transitions to idle and associated resources must be released.
Redirect differs from forward in that once forwarding has been set up, the operation is performed by TAPI, the service provider, or the switch without further involvement of the application. Redirect differs from transfer in that it does not require that the call first be answered.
Not all service providers support use of this operation.
TAPI 2: lineRedirect