I downloaded and ran the software upgrade/install/upgrade service for cmterm-7941_7961-sccp.8-4-4.cop.sgn
From reading, for this software to take effect you need to reboot the cluster.
In 4.x you could run the devicepack install and then type in the load name to test the new software before you did a cluster reboot. I tried to put in cmterm-7941_7961-sccp.8-4-4 as the load name but it did not work and i do not see the any cmterm-7491_7961 in the manage tftp files area.
Is there a similar method in 6.1 to test new software without doing a cluster reload?
Yes after a call to TAC. I imported correctly but, when searching though the software upgrade/tftp file manager I was useing cmterm and really its SCCP and you need to be exact on the case since this is now Linux. Also note that even though the name listed in the release notes is cmterm_7960_7961 that is not the real name its SCCP_xxx just like before.
I put the correct load name on the phone device and I was able to test the new code.
The way it worked for me looking for SCCP load files was to goto the OS Admin page, Software/Upgrades, TFTP File Management, change the search to contains then SCCP (all caps*) in the search field and you will see all the load files ex. SCCP41.8-4-2S.loads then just copy that file name in the firmware load fild of the device reboot the device and it will load the new code.
* If you don't use the exact case you will not find the file becuse of the way it searches. Linux go figure.
I have been using this method and it worked great for me testing new code. I hope this helps you.
I wish we had the ability to load the code in but not make it active. There are many times I would load new code and test it on a few phones then activate it during a window. It would be nice if we could upload the code without having to go back to change the default load to what it was before the upload.
Ahh, sorry, I forgot you had to stop/start the tftp service.
FYI, TAC wanted me to reboot the cluster to but, just restarting the TFTP service does the trick and does not place the new code in the default list for the rest of the devices like a cluster reboot would do.
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...