NB: Before you proceed to upgrade the servers, go to the Device menu. Choose Device Settings > Device Defaults and copy the phone load name that you currently use for the particular Cisco IP phone model which you dont want to upgrade. Paste this file name in a notepad so that you can use the same file name to revert the default phone load name to the old firmware for all other phones.
Then proceed to perform your upgrade. Once your upgrade is completed, the device defaults load file for all the phones will change.
Next go to the Device menu >Phone and choose the IP phone on which you want to keep the old firmware. Paste the old load information to the Phone Load Name field and click Update
Now you can reset all your phones.
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
1/ Complete the upgrade and switch versions on the CUCM.
2/ During the time of switch version or before it, make sure that the phones in the remote sites do not have access to the CUCM TFTP server. It would be better if you removed access to the CUCM servers completely for now. The TFTP server will contain all the configuration files of the phones with the new default firmware of the phones for ver 8.6.2
3/ Install the lower version of firmware for 79XX phones on version 8.6.2 (I'm not sure how far this is possible. Haven't tried this in my lab, whether one can install phone firmwares which are lower than the default for the CUCM version.)
4/ Set the Device Default Firmware for the 79XX phones to the older firmware which you installed in step 3 (and which the 79xx phones are already running)
5/ Reset the TFTP service so that the configuration files are updated with the new default firmware version.
6/ Remove the access lists on the remote routers and give the phones access to the CUCM.
I'm not very sure of Step 3, but if that works, then you should be able to execute this.
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...