I am currently working through a CCM upgrade from 4.1(2)SR1 -> 4.1(3) for purposes of the DST change. This is a CCM cluster of 2, and it is centralized for a total of 6 offices connected by full T1's.
I have gone through the upgrade documentation, and have no issues with the process. My question is, what is the best practice for handling all of the phones. So, I'll upgrade the Pub first, and the phones will be pointing to the Sub. Then, I'll upgrade the Sub, while the phones are pointing to the Pub. At what point do I actually restart the phones so that they'll get the new software? What's the best way to handle this?
When you perform the Cisco CallManager portion of the upgrade, you must upgrade one server at a time, so the subscriber servers can pull the replicas of the database from the publisher database server.
First upgrade the PUB, after PUB is up and running, failover the phones to PUB, then upgrade the SUB.
I would upgrade the firmware until both servers are up and running.
I get the order of upgrades, and the replicating DB to the Sub's, but I am more interested in the best way to handle the phones.
I also get that the phones will failover to the pub (already upgraded) while the sub is upgrading.
After completion of all of the upgrades with the pub and sub, how do I deal with the phones? After I upgrade the device pack on both pub/sub, do I restart all phones at the same time to get the new software? What's the best way to do that part of it?
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...