I am working with a customer to upgrade a CUCM 7.0 cluster to 9.1(1a).
As part of this I am trying to upgrade the firmware on phones connected to the 7.0 cluster to the default version for 9.1(1a)
The have some 7942G phones in a remote office which I have not managed to upgrade. The phones are registered to the cluster and can be reset via the CUCM interface but they will not load the new firmware version specified in the Phone Load Name field.
Looking at the network page of the phone web server I noticed that the fields relating to TFTP are blank -see below. I cannot remember ever seeing this and I am not sure how the phones managed to register.
The customer bought some new phones, configured them at their head office (where the DHCP scope has option 150 set) and then sent them to the remote office.
They were able to boot up using the local DHCP scope which does not have option 150 set and managed to register with the CUCM cluster. However the phones are not able to receive any updated config or firmware via TFTP.
I have found some phone remote control software and will try manually setting the TFTP server configs on the phones.
Can u also try doing telnet to call manager followed by tftp port from remote site PC to check whether tftp port is opened or not? you would get a blank screen which would be stable with blinking cursor which means port is working.
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...
[toc:faq]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 discusse...