/mcp• 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 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” 6. 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 IPv6 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 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 5 more times (as the same can again be enabled on Cisco Unified Communications Manager) before closing all the devices and provider. 7. Enterprise parameter “Enable IPv6” is disabled. Application tries to open a provider with IPv6 address. JTAPI will not be able to open a connection with CTI manager. Retry attempts are applicable only if connection gets established once, but since in this scenario even the first attempt is failing so there will be no subsequent reconnect attempts. Enterprise parameter “Enable IPv6” is enabled. Application does an open provider by providing the list of CTI Manager IPs as • IPv4 address of CTI Manager1 • IPv6 address of CTI Manager1 • IPv4 address of CTI Manager2 • IPv6 address of CTI Manager2 Now once the JTAPI is able to establish a connection with CTI Manager and later on if CTI Manager1 goes down, in failover attempt application can see delay in connecting as JTAPI will first try to connect with IPv6 address of CTI Manager1 (which is next in the list) even though that IP address is of the same CTI Manager and only onMangerce it times out it will try with the IPv4 address of the CTI Manager2 which will succeed (assuming CTI Manager2 is running). Calling Party IP Address Scenarios 1. Ipv6 enabled phone calls a CTI controllable device. Subsequently, the CTI controllable device is monitored by a JTAPI application. JTAPI will generate a CiscoCallCtlConnOfferedEv (non-Route Points) or CiscoRouteEvent (Route Points) notification containing an Ipv6 calling party IP address. getCallingPartyIpAddr() will return NULL getCallingPartyIpAddr_v6() will return the actual calling Party IPv6 address. 2. Ipv4 enabled phone calls a CTI controllable device. Subsequently, the CTI controllable device is monitored by a JTAPI application. JTAPI will generate a CiscoCallCtlConnOfferedEv (non-Route Points) or CiscoRouteEvent (Route Points) notification containing an Ipv4 calling party IP address (existing behavior) Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1151 Message Sequence Charts Calling Party IP Address Scenarios