<div dir="ltr">I had a similar issue with 8832s not getting an IP address running any firmware lower than 12.0.1SR2. Give this a shot:<div><br></div><div><br></div><div>* On CUCM Upgrade the firmware to the latest release.<br></div><div><div> * Boot the 8832 phone from inactive load.</div><div> * Hold the * key while connecting the power to the 8832.<br></div><div> * After the LED bar light turns ON green and then OFF, you can release the * key.<br></div><div> * The 8832 should proceed to boot from the image in the alternate partition.<br></div></div><div><br></div><div>Thanks,</div><div>DJ</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jun 10, 2018 at 9:54 AM, Jason Aarons (Americas) <span dir="ltr"><<a href="mailto:jason.aarons@dimensiondata.com" target="_blank">jason.aarons@dimensiondata.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div class="m_-2838053894661526520WordSection1">
<p class="MsoNormal">I would only deploy a device pack on new cluster build. All else per device update. I used to like to hardcode the load field on a per phone basis to prevent them from changing. Been doing less of that.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">The cmterm CE (Collaboration Endpoint) loads of 1.8GB are ridiculous, in DRS .tar backups too.<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> cisco-voip [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@<wbr>puck.nether.net</a>]
<b>On Behalf Of </b>Anthony Holloway<span class=""><br>
<b>Sent:</b> Monday, April 30, 2018 9:07 AM<br>
<b>To:</b> Charles Goldsmith <<a href="mailto:wokka@justfamily.org" target="_blank">wokka@justfamily.org</a>><br>
<b>Cc:</b> cisco-voip (<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>) <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Subject:</b> Re: [cisco-voip] 8832s<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal">I wish CUCM didn't ship with newer phone firmware.<u></u><u></u></p><div><div class="h5">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Since Cisco already drops support for all firmware older than the most recent firmware:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">- For each IP Phone model, once Cisco releases a new firmware version, the older versions are no longer supported.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">- Cisco expects customers who encounter a problem on an older version of firmware to test the latest firmware on a subset of phones in order to confirm that the problem still exists.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Source: <a href="http://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/unified-ip-phone-7900-series/116684-technote-ipphone-00.html" target="_blank">
http://www.cisco.com/c/en/us/<wbr>support/docs/collaboration-<wbr>endpoints/unified-ip-phone-<wbr>7900-series/116684-technote-<wbr>ipphone-00.html</a><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">And most people agree that you should upgrade firmware before a CUCM upgrade anyway, just remove firmware from CUCM.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Not too mention it clutters up TFTP.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I also think that the firmware should be decoupled from the Device Packs. When adding support for a single model phone, rarely am I also trying to upgrade 100% of the phones in the environment too.<u></u><u></u></p>
</div>
</div></div></div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Sun, Apr 29, 2018 at 8:22 PM Charles Goldsmith <<a href="mailto:wokka@justfamily.org" target="_blank">wokka@justfamily.org</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">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?<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Sun, Apr 29, 2018 at 7:06 PM Ryan Huff <<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">Sounds like the ole’ ‘step upgrade’ issue that plagued the 79xx series back in the 8.x days ....
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">My guess is they don’t actually need RMA’ed, just the easiest way to deal with it .... <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">In the 79xx series back in the day when I would perform this Lazarus trick for some lucky customers; the bootstrap filename was <b><span style="border:none windowtext 1.0pt;padding:0in">XMLDefault.cnf.xml. </span></b>Not sure if it’s the
same nowadays though.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><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/<wbr>support/docs/unified-<wbr>communications/unified-<wbr>communications-manager-<wbr>callmanager/200582-Update-<wbr>Cisco-IP-Phone-Firmware-<wbr>through-T.html</a><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">-Ryan-<u></u><u></u></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Apr 29, 2018, at 18:53, Jason Aarons (Americas) <<a href="mailto:jason.aarons@dimensiondata.com" target="_blank">jason.aarons@dimensiondata.<wbr>com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;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.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black">Does anyone have any ideas on what we could do to fix these phones other than RMAing them?<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black">Get
<a href="https://aka.ms/ghei36" target="_blank">
Outlook for Android</a><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><br>
<br>
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/<wbr>emaildisclaimer"</a>
<u></u><u></u></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">______________________________<wbr>_________________<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" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
<p class="MsoNormal">______________________________<wbr>_________________<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" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal">______________________________<wbr>_________________<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" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><u></u><u></u></p>
</blockquote>
</div>
</div></div><p class="MsoNormal"><br>
<br>
<span style="color:white">itevomcid</span> <u></u><u></u></p>
</div>
</div>
<br>______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">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/<wbr>mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">DJ Lundberg<div><br></div><div>Collaboration Engineer<br></div><div><a href="mailto:dj@netguys.net" target="_blank">dj@netguys.net</a></div><div>+1 763 225 2328</div></div></div>
</div>
<br>
<p>CONFIDENTIALITY NOTICE: The contents of this e-mail communication
and any attachments are intended solely for the addressee(s) and may contain
confidential and/or legally privileged information. If you are not the intended
recipient of this message or if this message has been addressed to you in
error, please immediately alert the sender by reply e-mail and then delete this
message and any attachments. If you are not the intended recipient, you are
notified that any use, dissemination, distribution, copying, or storage of this
message or any attachment is strictly prohibited.</p>