/mcp• CiscoAddrIntercomInfoRestorationFailedEv, on page 311 • Related Documentation, on page 289 • CiscoCall, on page 332 • CiscoProvider, on page 492 • CiscoTermEvFilter, on page 614 • CiscoTerminal, on page 617 • CiscoTerminalConnection, on page 636 • CiscoTermDeviceStateWhisperEv, on page 607 Intercom Support for Extension Mobility In Release 6.0(1) of Cisco Unified Communication Manager, support for intercom feature was added. Intercom feature requires destination to be auto-answered with one-way audio; therefore, no shared addresses can be configured for intercom. When user logs in by using Extension Mobility (EM) profile, it is possible to end up with shared address for intercom; so, currently extension mobility is not supported with intercom. Due to the wide use of extension mobility, this CIA is addressing the need to support intercom for extension mobility while still maintaining the single destination nonsharable nature of intercom addresses. This feature requires intercom addresses to be configured with default terminal, and allows configuring of intercom address on EM profile. When EM user logs in to a terminal with EM profile that is configured with an intercom address, intercom address is available only if default terminal of intercom address is same as terminal where user has logged in. If an intercom address is configured on terminal but default terminal for intercom address is not that terminal, intercom address does not appear on terminal. If this terminal is configured in the control list of Cisco Unified JTAPI application, JTAPI does not create intercom address in the provider domain. From Cisco Unified JTAPI point of view, there is no new interface or changes to support this feature. However, this feature introduces some transitional scenarios where intercom functionality may not work on intercom addresses. See the use cases. Backward Compatibility This feature is backward compatible. IPv6 Support This feature provides support for a nonsecure JTAPI connection in IPv6 only deployments. It enables Cisco Unified JTAPI applications to see the IPv6 address as the calling party address if the IPv6 support feature is enabled and if the Calling Party is using an IPv6-enabled phone. This feature supports the following functions: • Cisco Unified JTAPI exposes the new API canSupportIPv6() on the CiscoProviderCapabilities Interface to indicate whether Cisco Unified Communications Manager configuration is supporting IPv6. • Cisco Unified JTAPI closes the media or route terminal if there is a mismatch between what has been previously registered and what is currently configured. CiscoTermRegistrationFailedEv and the new reason code IP_ADDRESSING_MODE_MISMATCH are then sent as per this scenario. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 108 Features Supported by Cisco Unified JTAPI Intercom Support for Extension Mobility