/mcpif connection attempt fails with the first. If all the CTIManagers in the list are not available or if connection is refused by all CTIManagers, an exception gets sent to the application, and no further reconnection attempts occur. After the first successful connection, Cisco Unified JTAPI alternatively attempts to connect to the backup or primary CTIManager when a failure to CTIManager or connection to CTIManager is detected. The list of redundant CTIManagers designates a comma-separated list that is passed into the CiscoJtapiPeer.getProvider(String providerString) method as a String. The usage for the providerString follows: • providerString = CTIManager;login = XXX;passwd = YYY;appinfo = ZZZ (Non-redundant feature) • providerString = CTIManager1, CTIManager2;login = XXX, passwd = YYY;appinfo = ZZZ (Redundant feature) Because the appinfo parameter is optional, the application provides no specific appinfo parameter. Cisco Unified JTAPI generates one from a JTAPI instance ID and the local host name. Note Additionally, the jtapi.ini file may define different CTIManager lists to support the CiscoJtapiPeer.getServices() method. Cisco Unified JTAPI accepts the following definition: CtiManagers = <CTIManager1>, <CTIManager2>;<CTIManager3> where <CTIManager1>, <CTIManager2> specifies a redundant group. <CTIManager3> specifies a nonredundant group. From Unified CM Release 14SU3 onwards, support has been added to allow an application to specify a CTIManager as having least priority. Prior to this, all CTIManagers in a redundancy group have equal weightage. JTAPI would attempt to failover to the next availabe CTIManager in the group, if connection is lost or not established to the current server. This feature support is added to aid Dedicated Instance (DI) deployments that are cloud managed. It has been extended as a general usage API for all applications. An application needs to invoke setLeastPriorityCtiServer exposed on the <CiscoProvider>. Once a CTIManager is marked as least priority, JTAPI includes the configured CTIManager internally into the redundancy group. JTAPI attempts a connection to this CTIManager only if no other CTIManager is available. Once connected to the least priority CTIManager, JTAPI would deliver a CiscoProvConnToLeastPriorCtiServerEv on provider to indicate it is now connected to least priority CTIMaanger. JTAPI internally monitors availability or reachability to the other servers in the group. Once one of the servers are available, JTAPI would deliver a CiscoProvPrimNwReachableEv on the Provider observer to indicate one of the other servers are reachable now. JTAPI would later attempt a failover based on the configured fallback initiation time as specified by application via the API. If no time is specified, it would default to 10 min, post which JTAPI would forcefully failover application to the CTIManager which is available now. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 151 Features Supported by Cisco Unified JTAPI Invoking CTIManager Redundancy