<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi Jason,</div><div class=""><br class=""></div><div class="">Please try booting from the alternate image as Charles mentioned. Here is the process for the 8832 phones.</div><div class=""><br class=""></div><div class="">1. Hold the * key while connecting the power to the 8832.</div><div class="">2. After the LED bar light turns ON green and then OFF, you can release the * key.</div><div class="">3. The 8832 should proceed to boot from the image in the alternate partition.</div><div class=""><br class=""></div><div class="">The problem is caused by the older (downgraded) firmware not recognizing the USB-C to ethernet adapter the phone is using, therefore no network connectivity. If you can boot off the image that the phone came with the ethernet adapter will be detected.</div><div class=""><br class=""></div><div class="">We are making changes to prevent the phone from downgrading to a version that is not compatible with the connected ethernet adapter.</div><div class=""><br class=""></div><div class="">Joe</div><br class=""><div><div class="">On Apr 30, 2018, at 9:18 AM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca" class="">lelio@uoguelph.ca</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)" class="">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style class=""><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="blue" vlink="purple" class="">
<div class="WordSection1"><p class="MsoNormal">But in this case, it was “older” firmware on CUCM. <span style="font-family:"Segoe UI Emoji",sans-serif" class="">
☹</span><o:p class=""></o:p></p><p class="MsoNormal"><o:p class=""> </o:p></p><p class="MsoNormal">It’s not always very clear which version will be available in the CUCM version. I remember it was easy. They would list default firmware versions per version. Now it’s a bit harder to find.<o:p class=""></o:p></p><p class="MsoNormal"><o:p class=""> </o:p></p><p class="MsoNormal"><o:p class=""> </o:p></p><p class="MsoNormal"><o:p class=""> </o:p></p><p class="MsoNormal"><span style="font-family:"Arial",sans-serif" class="">---<o:p class=""></o:p></span></p><p class="MsoNormal"><b class=""><span style="font-family:"Arial",sans-serif" class="">Lelio Fulgenzi, B.A.</span></b><span style="font-family:"Arial",sans-serif" class=""> | Senior Analyst<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#333333" class="">Computing and Communications Services</span><span style="font-family:"Arial",sans-serif" class=""> | University of Guelph<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-family:"Arial",sans-serif" class="">Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-family:"Arial",sans-serif" class="">519-824-4120 Ext. 56354 |
<a href="mailto:lelio@uoguelph.ca" class=""><span style="color:#0563C1" class="">lelio@uoguelph.ca</span></a><o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-family:"Arial",sans-serif" class=""><o:p class=""> </o:p></span></p><p class="MsoNormal"><a href="http://www.uoguelph.ca/ccs" class=""><span style="font-family:"Arial",sans-serif" class="">www.uoguelph.ca/ccs</span></a><span style="font-family:"Arial",sans-serif;color:#1F497D" class=""> | @UofGCCS on Instagram, Twitter and Facebook<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-family:"Arial",sans-serif" class=""><o:p class=""> </o:p></span></p><p class="MsoNormal"><span id="cid:image001.png@01D3E063.B33D27B0"><image001.png></span><o:p class=""></o:p></p><p class="MsoNormal"><o:p class=""> </o:p></p><p class="MsoNormal"><b class="">From:</b> cisco-voip <<a href="mailto:cisco-voip-bounces@puck.nether.net" class="">cisco-voip-bounces@puck.nether.net</a>>
<b class="">On Behalf Of </b>Anthony Holloway<br class="">
<b class="">Sent:</b> Monday, April 30, 2018 9:07 AM<br class="">
<b class="">To:</b> Charles Goldsmith <<a href="mailto:wokka@justfamily.org" class="">wokka@justfamily.org</a>><br class="">
<b class="">Cc:</b> cisco-voip (<a href="mailto:cisco-voip@puck.nether.net" class="">cisco-voip@puck.nether.net</a>) <<a href="mailto:cisco-voip@puck.nether.net" class="">cisco-voip@puck.nether.net</a>><br class="">
<b class="">Subject:</b> Re: [cisco-voip] 8832s<o:p class=""></o:p></p><p class="MsoNormal"><o:p class=""> </o:p></p>
<div class=""><p class="MsoNormal">I wish CUCM didn't ship with newer phone firmware.<o:p class=""></o:p></p>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><p class="MsoNormal">Since Cisco already drops support for all firmware older than the most recent firmware:<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class="">
<div class=""><p class="MsoNormal">- For each IP Phone model, once Cisco releases a new firmware version, the older versions are no longer supported.<o:p class=""></o:p></p>
</div>
<div class=""><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.<o:p class=""></o:p></p>
</div>
<div class=""><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" class="">
http://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/unified-ip-phone-7900-series/116684-technote-ipphone-00.html</a><o:p class=""></o:p></p>
</div>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><p class="MsoNormal">And most people agree that you should upgrade firmware before a CUCM upgrade anyway, just remove firmware from CUCM.<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><p class="MsoNormal">Not too mention it clutters up TFTP.<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><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.<o:p class=""></o:p></p>
</div>
</div><p class="MsoNormal"><o:p class=""> </o:p></p>
<div class="">
<div class=""><p class="MsoNormal">On Sun, Apr 29, 2018 at 8:22 PM Charles Goldsmith <<a href="mailto:wokka@justfamily.org" class="">wokka@justfamily.org</a>> wrote:<o:p class=""></o:p></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" class="">
<div class=""><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?<o:p class=""></o:p></p>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
</div><p class="MsoNormal"><o:p class=""> </o:p></p>
<div class="">
<div class=""><p class="MsoNormal">On Sun, Apr 29, 2018 at 7:06 PM Ryan Huff <<a href="mailto:ryanhuff@outlook.com" target="_blank" class="">ryanhuff@outlook.com</a>> wrote:<o:p class=""></o:p></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" class="">
<div class=""><p class="MsoNormal">Sounds like the ole’ ‘step upgrade’ issue that plagued the 79xx series back in the 8.x days ....
<o:p class=""></o:p></p>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><p class="MsoNormal">My guess is they don’t actually need RMA’ed, just the easiest way to deal with it .... <o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><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.<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><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. <o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><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 class=""><span style="border:none windowtext 1.0pt;padding:0in" class="">XMLDefault.cnf.xml. </span></b>Not sure if it’s the
same nowadays though.<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><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.<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><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" class="">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><o:p class=""></o:p></p>
</div>
</div>
<div class="">
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><p class="MsoNormal">-Ryan-<o:p class=""></o:p></p>
</div>
</div>
</div>
<div class="">
<div class="">
<div class=""><p class="MsoNormal" style="margin-bottom:12.0pt"><br class="">
On Apr 29, 2018, at 18:53, Jason Aarons (Americas) <<a href="mailto:jason.aarons@dimensiondata.com" target="_blank" class="">jason.aarons@dimensiondata.com</a>> wrote:<o:p class=""></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt" class="">
<div class=""><p class="MsoNormal" style="margin-bottom:12.0pt"><o:p class=""> </o:p></p>
<div class=""><p class="MsoNormal"><span style="font-family: Arial, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
<div class=""><p class="MsoNormal"><span style="font-family: Arial, sans-serif;" class="">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" class="">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.<o:p class=""></o:p></span></p>
</div>
<div class=""><p class="MsoNormal"><span style="font-family: Arial, sans-serif;" class=""> <o:p class=""></o:p></span></p>
</div>
<div class=""><p class="MsoNormal"><span style="font-family: Arial, sans-serif;" class="">Does anyone have any ideas on what we could do to fix these phones other than RMAing them?<o:p class=""></o:p></span></p>
</div>
<div class=""><p class="MsoNormal"><span style="font-family: Arial, sans-serif;" class=""> <o:p class=""></o:p></span></p>
</div>
<div class=""><p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family: Arial, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
<div class="">
<div class=""><p class="MsoNormal"><span style="font-family: Arial, sans-serif;" class="">Get
<a href="https://aka.ms/ghei36" target="_blank" class="">Outlook for Android</a><o:p class=""></o:p></span></p>
</div><p class="MsoNormal"><span style="font-family: Arial, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div><p class="MsoNormal"><br class="">
<br class="">
This email and all contents are subject to the following disclaimer:<br class="">
<a href="http://www.dimensiondata.com/Global/Policies/Pages/Email-Disclaimer.aspx" target="_blank" class="">"http://www.dimensiondata.com/emaildisclaimer"</a>
<o:p class=""></o:p></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt" class="">
<div class=""><p class="MsoNormal">_______________________________________________<br class="">
cisco-voip mailing list<br class="">
<a href="mailto:cisco-voip@puck.nether.net" target="_blank" class="">cisco-voip@puck.nether.net</a><br class="">
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank" class="">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p class=""></o:p></p>
</div>
</blockquote>
</div>
</div><p class="MsoNormal">_______________________________________________<br class="">
cisco-voip mailing list<br class="">
<a href="mailto:cisco-voip@puck.nether.net" target="_blank" class="">cisco-voip@puck.nether.net</a><br class="">
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank" class="">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p class=""></o:p></p>
</blockquote>
</div><p class="MsoNormal">_______________________________________________<br class="">
cisco-voip mailing list<br class="">
<a href="mailto:cisco-voip@puck.nether.net" target="_blank" class="">cisco-voip@puck.nether.net</a><br class="">
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank" class="">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p class=""></o:p></p>
</blockquote>
</div>
</div>
</div>
_______________________________________________<br class="">cisco-voip mailing list<br class=""><a href="mailto:cisco-voip@puck.nether.net" class="">cisco-voip@puck.nether.net</a><br class="">https://puck.nether.net/mailman/listinfo/cisco-voip<br class=""></div></div><br class=""></body></html>