Extension Mobility failure after to do redundancy CallManager
My Customer have a CCM 5.1.3 working with Redudancy : one CCM Publisher and a one CCM Subscriber and are following problem: When The CallManager Publisher stayed down the user that are logged wiht extension mobility change to CallManager Backup and work normally, but, the user that is logoff don't obtain log in Extension Mobility. Any have Idea as solve this problem?
Re: Extension Mobility failure after to do redundancy CallManage
I believe the issue is that the extension state is held in a master database that is held on the publisher. EM enabled on subscribers as a service only allows the facility but the extension state is held in publisher database and then update the subscriber database. Therefore the database is not thier to record the state change
So if you are logged in you can recieve calls if you are not then you cant
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.