McDewey

CTI Manager Redundancy Handling with Least Priority CTI Server Set Scenario 1: Set least priority without specifying fallback Initiation time 1. Start application and set a CTIManager as least priority. Assume CTIManager redunancy list is CT1,CTI2,CTI3. 2. Application loses connectivity to CTI1. 3. Application loses connectivity to CTI3. 4. CTI1 is reachable now. 5. Fallback is started 5 min from now if a CTI server is reachable post it. 6. Post 5 min, CTI1 is still reachable. Events Action Application invokes CiscoProvider.setLeastPriorityCtiServer(CTI2). Application connects to CTI3. CiscoProvConnToLeastPriorCtiServerEv Application connects to CTI2. CiscoProvPrimNwReachableEv JTAPI is able to identify CTI1 reachability. Once connected to CTI1, JTAPI delivers CiscoProvFallbackToPrimNwCompltdEv event JTAPI initiates application fallback to CTI1 Scenario 2: Application initiates a forced fallback 1. Start application and set a CTIManager as least priority. Assume CTIManager redunancy list is CT1,CTI2,CTI3. 2. Application loses connectivity to CTI1. 3. Application loses connectivity to CTI3. 4. CTI1 is reachable now. 5. Application monitors if CTI2 is reachable now. Result Events Action Application invokes CiscoProvider.setLeastPriorityCtiServer(CTI2,600) where 600 is the fallback initiation time. Application connects to CTI3. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 806 Message Sequence Charts CTI Manager Redundancy Handling with Least Priority CTI Server Set