Can you "convert" a CM6.1 Subscriber to a Publisher ?
I have 3 servers in a single CM cluster. The second Subscriber is on a different site. In event of a DR scenario, and the primary site being lost(destroyed), I am left with a single Subscriber to continue call processing.
However, in this scenario, I would likely need to make some configuration changes (such as configuring new users, creating translation patterns - maybe changing pickup groups / hunt lists) and I believe this wont be possible with only a Subscriber active.
Is there a way that a Subscriber could be converted into a Publisher to facilitate these changes ? In this event, the original Publisher would be destroyed and would eventually be re-installed on new hardware (as a subscriber if necessary). So this isn't a role change I would look to flick back and forth - it would be a permanent change.
I would like to have this option documented - rather than rely solely on getting new hardware a rebuilding the Publisher from scratch before admin changes could be made, should this situation arise.
Re: Can you "convert" a CM6.1 Subscriber to a Publisher ?
Thanks. I would need to keep the sub in service, so I am thinking I would now build a new pub on new hardware.
If I was running the remaining sub - and got replacement hardware to build a replacement publisher on, could this be added to the cluster (and the live config on the sub being synced to the pub) - or would the pub need to be created from a DRS restore only ?
Could this be a DRS backup taken from the remaining sub, or would it need to have been from the original pub ?
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...