Proper procedure for overhauling our CCM 3.1.3(a) cluster to 3.3.3?
We currently have two Call Managers in cluster, both running CCM 3.1.3(a). One runs as a publisher, and the other as a subscriber. The subscriber acts as the DHCP server for our IP telephony subnet.
I have been suspect of both Call Managers for some time, as they have shown intermittent issues, on and off, ever since they were first implemented by a now decertified (first sign of alarm) Cisco IP Telephony VAR. So I want to do a fresh install of each one, using CCM 3.3.3.
What I'm really looking for is the proper steps for being able to remove each Call Manager from the cluster, rebuild it as a clean install of CCM 3.3.3 and reintroduce it back into the cluster so that the current CCM database can resynchronize so I don't have to reenter each users information. We only have 100 subscribers currently, so it wouldn't be a huge blow, but it would be time consuming.
Can anyone make any recommendations as to what steps would create the least down time for doing this?
All devices in our VOIP network have both CCMs in their DNS lists for fail over.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...