/mcpMessage Sequences Energywise Deep Sleep Mode, on page 923 Backwards Compatibility This feature is backward compatible. Extension Mobility Cross Cluster This feature allows users to log in to an IP phone registered to a cluster with user profiles configured with another cluster. The Extension Mobility feature allows a user to log in to an IP phone to appear as user's desk phone temporarily, subject to the administrative policy. After logging on to an IP phone, the user can receive incoming calls normally routed to the user's desk phone and retain the personalized configuration, such as speed dials, services links and other user-specific properties. Currently, Extension Mobility service is limited to a single Cisco Unified Communications Manager (Cisco Unified Communications Manager) cluster. A user provisioned in one cluster today cannot log in to an IP phone of another cluster with the Extension Mobility feature, even though both clusters may belong to the same enterprise. This limitation is overcome with the introduction of this new feature, which allows the user provisioned in one cluster to log in to an IP phone of another cluster. With the existing behavior, when a user logs in to a terminal with a user ID that matches the user ID used by Cisco Unified Communications Manager JTAPI application, the terminal is treated as part of the control list and application is able to add call observer on the terminal and/or address. As part this feature support, Extension Mobility profiles can be added to the user's control list via the Cisco Unified Communications Manager Admin pages. When a user uses Extension Mobily to log into a device using a profile in the control list, JTAPI delivers CiscoAddrCreatedEv and CiscoTermCreatedEv, and application can add call observer to control the terminal or address. JTAPI exposes getCiscoCause () API on all provider events. For provider events associated with non-Extension Mobility login or logout scenarios, the cause delivered will be CiscoProvEv.NORMAL. For provider events associated with Extension Mobility login or logout scenario, the cause may be any of the below depending on the type of Extension Mobility login or logout: CiscoProvEv.CAUSE_EM_LOGIN CiscoProvEv.CAUSE_EM_LOGOUT CiscoProvEv.CAUSE_EM_LOGIN_PROFILE_ADD CiscoProvEv.CAUSE_EM_LOGOUT_PROFILE_REMOVE Interface changes explain more about each of these causes. The following is a complete set of provider events that have API getCiscoCause(): CiscoAddrActivatedEvCiscoAddrActivatedOnTerminalEv CiscoProvFeatureEv CiscoProvTerminalCapabilityChangedEv CiscoAddrRestrictedEv CiscoTermActivatedEv CiscoTermRestrictedEv CiscoAddrCreatedEv CiscoTermCreatedEv CiscoAddrRemovedEv CiscoTermRemovedEv Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 92 Features Supported by Cisco Unified JTAPI Extension Mobility Cross Cluster