/mcpaddress of CTI Manager1 (which is next in the list) even though that IP address is of the same CTI Manager and only once it times out it will try with the IPv4 address of the CTI Manager2 which will succeed (assuming CTI Manager2 is running). Provider Open Scenario 1. Service Parameter for Reconnect Attempt is not set(or set to 0), Enterprise parameter “Enable IPv6” is disabled. Application tries to open a provider with IPv4 address. JTAPI will be able to open a connection with CTI manager. • CTI Manager is stopped – JTAPI will try reconnecting to CTI manager indefinitely till the CTI Manager is stared again and connection is restored. • Enterprise parameter “Enable IPv6”is enabled and CTI manager is restarted – JTAPI will be able to reconnect to CTI Manager with the same IPv4 address. 2. Service Parameter for Reconnect Attempt is not set (or set to 0), Enterprise parameter “Enable IPv6” is enabled. Application tries to open a provider with IPv4 address. JTAPI will be able to open a connection with CTI Manager. • CTI Manager is stopped – JTAPI will try reconnecting to CTI manager indefinitely till the CTI Manager is stared again and connection is restored. • Enterprise parameter “Enable IPv6”is disabled and CTI manager is restarted – JTAPI will be able to reconnect to CTI Manager with the same IPv4 address. But, the existing devices registered with IPv6 address will be closed with “CiscoTermRegistrationFailedEv” with a new reason code “IP_CAPABILITY_MISMATCH” 3. Service Parameter for Reconnect Attempt is not set (or set to 0), Enterprise parameter “Enable IPv6” is enabled. Application tries to open a provider with IPv6 address. JTAPI will be able to open a connection with CTI Manager. • CTI Manager is stopped – JTAPI will try reconnecting to CTI manager indefinitely till the CTI Manager is started again and connection is restored. • Enterprise parameter “Enable IPv6”is disabled and CTI manager is restarted – JTAPI will not be able to reconnect to CTI Manager, as it no longer supports IPv6 address but JTAPI will try reconnecting to CTI Manager indefinitely till the time service parameter is again enabled and CTI Service restarted. 4. Service Parameter for Reconnect Attempt is set to some integer value (say 5), Enterprise parameter “Enable IPv6” is disabled. Application tries to open a provider with IPv4 address. JTAPI will be able to open a connection with CTI manager. • CTI Manager is stopped – JTAPI will try reconnecting to CTI manager 5 times before closing all the opened devices and provider. • Enterprise parameter “Enable IPv6”is enabled and CTI manager is restarted – JTAPI will be able to reconnect to CTI Manager with the same IPv4 address. 5. Service Parameter for Reconnect Attempt is set to some integer value (say 5), Enterprise parameter “Enable IPv6” is enabled. Application tries to open a provider with IPv4 address. JTAPI will be able to open a connection with CTI Manager. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1150 Message Sequence Charts Provider Open Scenario