I'm trying to get a 9971 working with CUCM 126.96.36.19900-5 and it's stuck on the final file of a load pack, hoping someone can help/shed light.
The device looks like it rolled back it's .load file when it was originally plugged into our network. Originally, when the phone came online, it came up on our old pub/sub configuration. When I noticed this I did a factory reset on the phone, but it still came up on the wrong pub/sub.
At this point I manually pointed the phone to the new TFTP servers in the IPv4 Setup menu and restarted it, it was only then that I noticed that the scope on the VLAN it had initially landed on was pointing to an old TFTP/CUCM location.
I have since updated the scope, but the phone is now stuck in an upgrading state not registering with CUCM.
Things I can see:
Top banner has: Phone Not Registered and the spinning wheel
In the Phone Information menu I can see "Upgrade in Progress", it is on Active Load sip9971.9-0-3 and attempting to load 9971.9-2-4-19.
Drilling into the Details the phone loads all files, then gets stuck on the final one, which is called: rootfs9971.9-2-4-19.sebn
I cannot access any of the settings to change them/ do a factory reset via the Administrator Settings (everything greyed out)
In the Status Messages I see: "TFTP Error: ram/SEPE84040A3245B.cnf.xml" and File Not Found:SEPE84040A3245B.cnf.xml"
So I'm confused. Looking at the TFTP locations that I have pointed the phone to, I can see the
rootfs9971.9-2-4-19.sebn file present. I'm under the impression that I shouldn't need the <Mac>.cnf.xml file as it will just use the defaults for that model.
I've tried debugging the TFTP logs using the RTMT, but haven't had much luck figuring out how I'm meant to be checking these logs and what to look at. I've also tried pointing the phone to a standalone Linux TFTP server to debug it, which always worked fine in the past with 7960s, however the phone isn't hitting that server when I direct it there via DHCP.
Basically I think I've inadvertently hardcoded the TFTP settings on the phone (Alternate TFTP set to Yes) and it is no longer getting TFTP addresses from DHCP (from what I can tell). Can anyone tell me how to reset this phone when all of the settings are greyed out and non-responsive? I need a hard reset along the lines of 3491672850*# or 123456789*0# on the 7960s....I can't get into the Administrator Settings.
You can try the same factory reset procedure as the 79XX phones.
Step 1) While powering up the phone, press and hold #.
Step 2) When the light on the mute button and handset light strip turns off and all other lights (line button, headset button, speakerphone button and select button) stay green, press 123456789*0# in sequence.
When you press 1, the lights on the line buttons turn red. The light on the select button flash when a button is pressed.
If you press the buttons out of sequence, the lights on the line button, headset button, speakerphone button, and select button turn green. You will need to start over and press 123456789*0# in sequence again.
After you press these buttons, the phone goes through the factory reset process.
Do not power down the phone until it completes the factory reset process, and the main screen appears.
So I managed to perform a factory reset by powering the phone up on a PoE port whose VLAN was not configured with the TFTP scope, that stopped the phone attempting to update and allows access to the menu settings to do the reset. This would work using a power brick as well I imagine.
The problem remains though, the phone is still stuck on upgarding the final file in the load: rootfs9971.9-2-4-19.sebn
Is anyone aware of a problem going from load sip9971.9-0-3 to sip9971.9-2-4-19? Do I need to use an intermediate load to follow this upgrade path?
It appears part of the problem with this phone was that the phone profile didn't have a number assigned on line 1 and was SIP protocol. Apparently if there is no number there, the phone can't register.
The thing that worked in the end was (as I had no phone profile present, possibly deleted during earlier fix attempts):
Manually created the phone in CME using it's MAC, copying out settings from a working 9971 (SIP protocol)
Assigned the phone a number on line 1
Factory reset the phone
When the phone came back up it discovered the .cnf file without issue and successfully upgraded and registered.
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...