<div dir="ltr">Since the 8832 is a dual bank phone, shouldn't it have the old image on it in the backup bank? Maybe hardcoding the old image on the phone configuration and doing a reset will cause it to boot from it?<div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Apr 29, 2018 at 7:06 PM Ryan Huff <<a href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
Sounds like the ole’ ‘step upgrade’ issue that plagued the 79xx series back in the 8.x days ....
<div><br>
</div>
<div>My guess is they don’t actually need RMA’ed, just the easiest way to deal with it .... </div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>In the 79xx series back in the day when I would perform this Lazarus trick for some lucky customers; the bootstrap filename was <span style="margin:0px;padding:0px;border:0px;font-weight:700;font-stretch:inherit;line-height:inherit;vertical-align:baseline;background-color:rgba(255,255,255,0)">XMLDefault.cnf.xml. </span>Not
sure if it’s the same nowadays though.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div><a href="https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200582-Update-Cisco-IP-Phone-Firmware-through-T.html" target="_blank">https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200582-Update-Cisco-IP-Phone-Firmware-through-T.html</a></div></div><div dir="auto"><div><br>
<div><br>
</div>
<div>-Ryan-</div></div></div><div dir="auto"><div>
<div><br>
On Apr 29, 2018, at 18:53, Jason Aarons (Americas) <<a href="mailto:jason.aarons@dimensiondata.com" target="_blank">jason.aarons@dimensiondata.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><br>
<br>
<div align="left">
<div dir="auto" style="direction:ltr;margin:0;padding:0;font-family:sans-serif;font-size:11pt;color:black">
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0;padding:0;font-family:sans-serif;font-size:11pt;color:black">
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 <a href="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" target="_blank">factory
reset</a> 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.<br>
</div>
</div>
<div align="left">
<div dir="auto" style="direction:ltr;margin:0;padding:0;font-family:sans-serif;font-size:11pt;color:black">
<br>
</div>
</div>
<div align="left">
<div dir="auto" style="direction:ltr;margin:0;padding:0;font-family:sans-serif;font-size:11pt;color:black">
Does anyone have any ideas on what we could do to fix these phones other than RMAing them?<br>
</div>
</div>
<div align="left">
<div dir="auto" style="direction:ltr;margin:0;padding:0;font-family:sans-serif;font-size:11pt;color:black">
<br>
</div>
</div>
<div dir="auto" style="direction:ltr;margin:0;padding:0;font-family:sans-serif;font-size:11pt;color:black">
<br>
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0;padding:0;font-family:sans-serif;font-size:11pt;color:black">
<div dir="auto" style="direction:ltr;margin:0;padding:0;font-family:sans-serif;font-size:11pt;color:black">
Get <a href="https://aka.ms/ghei36" target="_blank">Outlook for Android</a></div>
<br>
</div>
<br>
<br>
<font>This email and all contents are subject to the following disclaimer:<br>
<a href="http://www.dimensiondata.com/Global/Policies/Pages/Email-Disclaimer.aspx" target="_blank">"http://www.dimensiondata.com/emaildisclaimer"</a>
</font><font color="white"></font></div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</div>
</blockquote>
</div></div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>