Anyone know of any way to do Inter-Cluster Mobility?
I have a customer who has 3 sites. Each Executive will have an IP Phone at each site (shared DN across all 3 sites so that they don't miss their calls when they travel between sites).
Each of the 3 sites is a different CallManager Cluster.
What's the best way to accomplish this?
The only way I see is to
1. Statically configure the IP Phones to point to the user's home CallManager Cluster.
2. Create a shared DN for each IP Phone at each site.
Problems... 911 or local site dialing for these users. Since you can't share gateways between callamanger clusters, you'd have to provision a separate gateway at each site for 911 or local site dialing just to accomplish the above. I'd then have to add a separate DN for each site and instruct the user to use that site specific extension for local and 911 dialing!
Re: Intercluster IP Phone Mobility??? Or Workaround?
Intercluster EM will not work.
The following restrictions apply to Cisco CallManager Extension Mobility:
Cisco CallManager Extension Mobility works on phones within a single Cisco CallManager cluster only.
Cisco CallManager Extension Mobility supports a maximum of 2000 login and logout operations per hour. Remember that these operations are sequential, not concurrent.
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.
If the User Locale that is associated with the login user or profile is not the same as the locale or device, after a successful login, the phone will perform a restart followed by a reset. This occurs because the phone configuration file is being rebuilt. Addon module mismatches between profile and device may have the same behavior.
Cisco CallManager Extension Mobility requires a physical Cisco IP Phone for login. Users of office phones that are configured with Cisco CallManager Extension Mobility cannot log in to their phones remotely.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...