Hi guys, we have CUCM with version 8.6, firmware for 7962 is SCCP42.9-2-1S installed in CUCM. All the existing 7962 phone are in same firmware. Recently we have purchase a numbe of new 7962 phone. The oringal firmware in the new phone is SCCP42.9-3-1SR1-1S.
Now the problem: after connect those new phone, it try to downgrade it's firmware to 42.9-2.1S, and once it load the 42.9-2.1S, it keeping goes back to the upgrading window then reboot itself again. I have pluge those new in the CME enviroment. register straight away. for testing purpose I also try change the file name to 42.9-3 in CUCM default setting, phone boots and did not go to the upgade window, but register has been reject, after manually add the phone, phone register. seem to me the problem is that the firwmare with version 42.9-2 for some reason is not working properly in the new 7962 phones.
Question: my understanding is that if the phone firmware has lastest version than one in TFTP server, it should keep the lastest version without download from TFTP. Also how can I prevent those new phone to be downgrade to the old firmware from TFTP in future.
A phone will upgrade/downgrade to whatever file is available on its tftp server. If you dont want the phone to downgrade to the firmware on the tftp server then you need to install the 9.3 firmware on CUCM and set the phone load for this particular phone to use it. Be careful when you do this, dont restart your tftp service/server because this will force all your phones to upgrade to the latest firmware
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
Hi Rob, thanks for sharing this with us. Yes you are right, I have checked my old 7962, it's hardware version is 14; but the new one is 16.
The interesting thing is that in my first box of 8 new 7962 phone, they all have been registered without any problem, but every time when it connected, the upgrade window display and indicates it try to upload the old firmware 42.9-2 from CUCM, but after a few second it reboot and skip the upgrading window and go through to register with CUCM via it's new firmware. this process happens every time when connected those phone. So seem to me, these 8 phones has the ability to skip the default firmware defined in cucm device setting and use it's own newer firmware(42.9-3), while other phone don't, which end up with uploaded incompatible firmware (42.9-2)
I thought that all the phone with latest firmware will automatically skip from downloading the old firmware (this true in my lab), but seem to me this is not the case, can anyone here from Cisco to confirm?.
Now my question is how to stop those new phone from being automatically uploaded with the old firmware 42.9-2.1S from TFTP server.
I am aware of the option to upload the new firmware to CUCM and but I don't want to affect hundreds of existing phone. I can solve this issue by forcing them to user the old version via the phone load field in each phone's device information page but I believe there must be some better option than that. Any other suggestion?
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...