/mcpgetCallingPartyIpAddr() will return the actual calling Party IPv4 address. getCallingPartyIpAddr_v6() will return NULL. 3. Ipv6 only phone calls a CTI controllable device that is already 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 4. Ipv4 enabled phone calls a CTI controllable device that is already monitored by a JTAPI application. JTAPI will generate a CiscoCallCtlConnOfferedEv (non-Route Points) or CiscoRouteEvent (Route Points) notification containing an Ipv4 formatted calling party IP address. getCallingPartyIpAddr() will return the actual calling Party IPv4 address. getCallingPartyIpAddr_v6() will return NULL. 5. Ipv4_v6(Two Stack) 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 and Ipv6 calling party IP addresses. getCallingPartyIpAddr() will return the actual calling Party IPv4 address. getCallingPartyIpAddr_v6() will return the actual calling Party IPv6 address 6. Ipv4_v6(Two Stack) phone calls a CTI controllable device that is already monitored by a JTAPI application. JTAPI will generate a CiscoCallCtlConnOfferedEv (non-Route Points) or CiscoRouteEvent (Route Points) notification containing an Ipv4 and Ipv6 calling party IP addresses. getCallingPartyIpAddr() will return the actual calling Party IPv4 address. getCallingPartyIpAddr_v6() will return the actual calling Party IPv6 address RTP Addresses 1. An Ipv6 enabled phone calls an Ipv6 JTAPI Observed phone and the call is answered. JTAPI will generate: • CiscoRTPOutputStartedEv containing the far-end Ipv6 RTP address. • CiscoRTPInputStartedEv containing the Ipv6 RTP address of the monitored phone. 2. An Ipv4 enabled phone calls an Ipv4 JTAPI Observed phone and the call is answered. JTAPI will generate(existing behavior): • CiscoRTPOutputStartedEv containing the far-end Ipv4 RTP address. • CiscoRTPInputStartedEv containing the Ipv4 RTP address of the monitored phone. 3. An Ipv4 enabled phone calls an Ipv6 JTAPI Observed device and the call is answered. JTAPI will generate: • CiscoRTPOutputStartedEv containing the far-end Ipv6 RTP address which corresponds to the MTP that was automatically inserted by Call Manager to perform Ipv4/Ipv6 conversion. • CiscoRTPInputStartedEv containing the Ipv6 RTP address of the monitored phone. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1152 Message Sequence Charts RTP Addresses