I have a question regarding an upgrade procedure from 3.3(3) to 3.3(5) then to 4.2(3). The upgrade will be done using a new MCS server.
I was wondering if I could do a BARS restore from the current 3.3(3) server to the new 3.3(3) server, upgrade the new server to 3.3(5) and remove the subscribers from the databse without them being online, and then do the 4.2(3) upgrade?
What I would like to do, is do the upgrade on a stand alone Publisher, and then rebuild the subscribers as a fresh 4.2(3) Subscriber and then add them back into the cluster.
I have read the upgrade procedures so plesae don't post a PDF of the upgrade guide.
The steps you have mentioned and plan to do sounds like the right way to go ahead with the Process. Only thing you will have to keep in mind is that the new Publisher should be kept in a different StandAlone Network as the server would have the same hostname and IP Address. So the server should be in a Network which cannot access the current CallManager cluster.
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...