/mcpthis call exposes other Call Model Objects such as the associated Addresses, Connections, and so on. The extension also defines additional errors for the application. Caller Options Summary In the absence of a callback, or if RouteSession.routeSelect() or endRoute() has not responded to a routeEvent, the caller receives nothing until • The application can disconnect() or reject() the connection on the Route Point, and, thereby, the caller receives a busy tone. • The application can accept the call, and the Forward No Answer, if configured, kicks in. • The application can drop the call. The caller holds the receiver but does not know what happened. With a callback, if the application chooses to call an endRoute(), after endRoute() returns, the caller receives a ringback until • The client calls a disconnect() that would drop the call. • The client redirects() the call. • The forward on no answer timer that is configured via the scm.ini will kick in and forward the call unless the preceding two options have already kicked in. • If no forwarding is configured for the Route Point, the caller continues to receives a ringback unless the first two options kick in. Fault Tolerance When Using Route Points One way for an application that uses route points to deal with fault tolerance requires connecting two JTAPI applications to two different Cisco Unified Communications Managers, each registering a different RouteAddress. For example, Application1 manages RouteAddress1 by using Communications Manager1. Application2 manages RouteAddress2 by using Communications Manager2. In Cisco Unified Communications Manager Administration, ensure the ForwardNoAnswer configuration for these CTI Route Points is administered, so they point to each other. In this example, RouteAddress1 would have FNA = RouteAddess2, and RouteAddress2 would have FNA = RouteAddress1. If Communications Manager1 goes down, calls forward to RouteAddress2, so Application2 takes over. Furthermore, both applications could be configured to reconnect to the proper Cisco Unified Communications Manager server when they receive a ProviderShutdown event. Secure Conferencing This feature informs applications whether a call is secure, allowing for secure conference calls. When the overall security status of the call changes, secure conferencing provides applications with a notification in the form of an event on the call. Applications receive the overall call security status of the call in the CiscoCallSecurityStatusChangedEv when the overall call security status changes. When a terminal goes to the talking state, JTAPI provides the call security status information to the applications. Applications can query the security status of the call by using a new interface on CiscoCall. The system makes the security status information available to applications when the applications start monitoring an existing call. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 155 Features Supported by Cisco Unified JTAPI Caller Options Summary