I'm in the process of preparing a new hardware platform to replace an existing publisher with the exact same configuration. All went well, same versions and patches etc., I have backed up config on the old and restored config on the new machine and so on, except for one thing: I cannot find the network locale for Belgium anymore in the list when configuring IP phones. Despite having installed the one and only "combined" network locale installer for 4.2 found on CCO. On the currently - old - but live publisher, Belgium is indeed a valid option in the list on the ip phone config. The customer obviously expects the same config/support on his new machine. Can anyone help me re-install support for the Belgium network locale on CCM 4.2(3) ?
* You must install Cisco Unified CallManager 4.2(3) on every server in the cluster before you install the Cisco Unified CallManager Locale Installer. Ensure the locale installer is installed on every server in the cluster (install on the Publisher server before the Subscriber servers).
* You must reboot the server for the changes to take effect. After you complete all locale installation procedures, restart each server in the cluster. Updates do not occur in the system until you restart all servers in the cluster; services restart after the server reboots.
Yep, aware of that document, been there, done that, double-checked again, read the release notes, doesn't fix my problem.
The point is, when one progressively upgrades through various versions starting from about 3.3 to 4.2(3), the network locale for Belgium is available. Apparently the locale migrates along from previous versions.
For me, this is no longer an option, I am to replace that machine with a new one, on which I have installed from the beginning 4.2(3) without starting out from earlier versions.
I see all the network locales for other countries now appear after running the combined locale installer, but Belgium no longer is one of them. Not even in the list of countries supported presented by the installation wizard during installation ...
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.