McDewey

Cisco Extension Mobility Restrictions When database replication within the Cisco Unified Communications Manager cluster is not functioning per expectation, it impacts the extension mobility functionality. To improve resiliency, we recommend the following: • Configure the backup CCM service, TFTP service, and extension mobility service in an alternate data center. • Use a load balancer to send the extension mobility login request to the extension mobility service in different data centers in a round robin method such that the extension mobility service in another data center can handle the requests when the first is unreachable. • Use the backup extension mobility URL to log in when the primary URL fails. Note Table 34: Cisco Extension Mobility Restrictions Restriction Feature Cisco Extension Mobility maintains a cache of all logged-in user information for 2 minutes. If a request comes to extension mobility about a user who is represented in the cache, the user is validated with information from the cache. For example, if a user changes the password, logs out, and then logs back in within 2 minutes, both the old and new passwords are recognized. Cache When a Cisco Extension Mobility user logs out of a device, all call back services that are active for the Cisco Extension Mobility user are automatically canceled. Call Back The characters that display when a user logs in depend on the current locale of the phone. For example, if the phone is currently in the English locale (based on the Logout profile of the phone), the user can only enter English characters in the UserID. Character Display Cisco Extension Mobility does not support the hold reversion feature. Hold Reversion Cisco Extension Mobility requires a physical Cisco Unified IP Phone for login. Users of office phones that are configured with Cisco Extension Mobility cannot remotely log in to their phones. IP Phones If the user locale that is associated with the user or profile is not the same as the locale or device, after a successful login, the phone will restart and then reset. This behavior occurs because the phone configuration file is rebuilt. Addon-module mismatches between profile and device can cause the same behavior. Locale If Cisco Extension Mobility is stopped or restarted, the system does not automatically log out users who are already logged in after the logout interval expires. Those phones automatically log out users only once a day. You can manually log out these users from either the phones or from Cisco Unified CM Administration. Log Out Cisco Extension Mobility and join across line services are disabled on protected phones. Secure Tone Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 415 Receiving Calls Cisco Extension Mobility Restrictions