Since this morning, all our 7942 phones started upgrading, if you reset the phone. By resetting, I do not mean the reset to factory defaults, but a normal reset.
The latest version of the firmware we have on our CUCM version8 is 9.2SR2
I can see that in the firs stage the phone is requesting files from the TFTP server, and gets the correct files for the 42 / 62 series. The first part goes perfectly.
After rebooting, the telephone starts upgrading again, but there the error auth fails is shown at the display. after a few seconds, the phone reboots, but starts upgrading again. The phone stays in this loop until I unplug it, or reset it to factory defaults.
Resetting to factory defaults is also no option, because I get stuck at the same point.
I also noticed that the telephone requests the file SCCP41.9-0-2SR1S, which looks strange to me, because this is a file for the 41/61 series?
What version of firmware is the phone upgrading from? If it is prior to 8.5(2) you will have to first upgrade to exactly 8.5(2). After the phone has that you can proceed into 9.x. The code signing key changed and the phone will not trust a newer firmware load until it has the new key which is embedded in the 8.5.2 build.
I checked the CUCM and the frimware version on the default settings of the phones is 9.2 SR2. Loking at this, it is normal that the phones start upgrading after reset, since it is a newer firmware version. One of the network guys overhere, did put the new firmware on the system without telling me
The firmware on the phones is 9.0.2 SR1, so in the upgrade path this shouldn't be a problem.
I also tested with a phone out of the box, with the same firmware (9.0.2 SR1) and this one is updating perfectly.
This pone is not yet created in CUCM.
I did the test with one of the phone in production (deleting the device in CUCM) and guess what, it updated like a charm .
After this, I re - created the phone in CUCM. After a restart of the phone, it went to updating locale settings and did a reboot. After this everything was working again.
After this experience, I checked the other phones, but could not find anything strange in their configuration. Lucky for me it is only the 7942 model that has this problem (we have only 10 ) at our site
Looking at this experience, I rather find it strange that somewhere in the upgrade path, something goes wrong if the phone is already registered in CUCM. I think it is commonly used to update already existing phones to a newer firmware. We also did this before.
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...