Sounds like the ole’ ‘step upgrade’ issue that plagued the 79xx series back in 
the 8.x days ....

My guess is they don’t actually need RMA’ed, just the easiest way to deal with 
it ....

I’d flash the phones and advertise an isolated tftp server to them with the 
firmware load and XML bootstrap file. The phones aren’t working now, so 
flashing them and then still not getting them to load right isn’t going to make 
it any worse.

Use DNS in the DHCP scope in your isolation network with the TFTP server and 
pcap/debug the DNS queries to see the bootstrap and load files it’s looking for.

In the 79xx series back in the day when I would perform this Lazarus trick for 
some lucky customers; the bootstrap filename was XMLDefault.cnf.xml. Not sure 
if it’s the same nowadays though.

Here is the Cisco doc on the procedure for the older stuff .... worth a shot 
but not sure if it still works on the newer gear.

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200582-Update-Cisco-IP-Phone-Firmware-through-T.html

-Ryan-

On Apr 29, 2018, at 18:53, Jason Aarons (Americas) 
<[email protected]<mailto:[email protected]>> wrote:




I have a customer with four 8832 conference room phones. Their CUCM was running 
version 12.0.1 of the 8832 firmware. These phones shipped with version 
12.0.1SR2. When they registered the first two phones they downgraded from 
12.0.1SR2 to 12.0.1 and are now unusable. They sit on “Connecting” after 
booting up. They do not get an IP address. You cannot set an IP address 
manually. If you reset the phone it doesn’t fix it, nor does a factory 
reset<https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8832/english/adminguide/cs88_b_conference-8832-admin-guide-cucm/cs88_b_conference-8832-admin-guide-cucm_chapter_01011.html>
 allow the phone to revert to the firmware they shipped with. Cisco TAC says 
they must be RMA’d. We upgraded CUCM to 12.0.1SR3 and the other two phones 
upgraded fine from 12.0.1SR2 to 12.0.1SR3.

Does anyone have any ideas on what we could do to fix these phones other than 
RMAing them?



Get Outlook for Android<https://aka.ms/ghei36>



This email and all contents are subject to the following disclaimer:
"http://www.dimensiondata.com/emaildisclaimer";<http://www.dimensiondata.com/Global/Policies/Pages/Email-Disclaimer.aspx>
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to