<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
One last though Bill,<br>
<br>
IMO, the best way to deal with the old 79xx's that had the intermediary firmware upgrade issue is to manually upgrade it offline.<br>
<br>
- Download and unzip all the firmware file for the load version into a folder on your PC (source the firmware ZIP file from CCO)<br>
- get a tftp client (TFTP32, tftpd ... etc) and point it at that folder<br>
- put a file named "XMLDefault.cnf.xml" in that folder too<br>
- put the following contents in the XML file<br>
<blockquote>
<blockquote><i><font size="-1"><Default></font></i><br>
<i><font size="-1"> <callManagerGroup></font></i><br>
<i><font size="-1"> <members></font></i><br>
<i><font size="-1"> <member priority="0"></font></i><br>
<i><font size="-1"> <callManager></font></i><br>
<i><font size="-1"> <ports></font></i><br>
<i><font size="-1"> <ethernetPhonePort>2000</ethernetPhonePort></font></i><br>
<i><font size="-1"> <mgcpPorts></font></i><br>
<i><font size="-1"> <listen>2427</listen></font></i><br>
<i><font size="-1"> <keepAlive>2428</keepAlive></font></i><br>
<i><font size="-1"> </mgcpPorts></font></i><br>
<i><font size="-1"> </ports></font></i><br>
<i><font size="-1"> <processNodeName></processNodeName></font></i><br>
<i><font size="-1"> </callManager></font></i><br>
<i><font size="-1"> </member></font></i><br>
<i><font size="-1"> </members></font></i><br>
<i><font size="-1"> </callManagerGroup></font></i><br>
<i><font size="-1"> <loadInformation>*** THE FILENAME OF THE .LOADS FILE, WITHOUT THE .LOADS EXTENSION</loadInformation></font></i><br>
<i><font size="-1"> <authenticationURL></authenticationURL></font></i><br>
<i><font size="-1"> <directoryURL></directoryURL></font></i><br>
<i><font size="-1"> <idleURL></idleURL></font></i><br>
<i><font size="-1"> <informationURL></informationURL></font></i><br>
<i><font size="-1"> <messagesURL></messagesURL></font></i><br>
<i><font size="-1"> <servicesURL></servicesURL></font></i><br>
<i><font size="-1"></Default></font></i><br>
</blockquote>
</blockquote>
<div class="moz-cite-prefix">- Put your PC and the phone on an isolated network / vlan and create a DHCP scope that offers Option 150, which points at the ip of the tftp server (your PC, in this case)<br>
- Boot the phone on this network and it should upgrade. Do this for all the incremental versions.<br>
<br>
Thanks,<br>
<br>
Ryan<br>
<br>
On 06/30/2016 10:36 AM, Ryan Huff wrote:<br>
</div>
<blockquote cite="mid:BLUPR18MB0482E828BEA4830F72223AF8C5240@BLUPR18MB0482.namprd18.prod.outlook.com" type="cite">
<p>Bill,</p>
<p>To fix the factory-reset 7941 phone (I'm assuming this means you used # + 123456789*0#), you'll need to first upgrade it to the intermediate 8.3(3), then 8.5(2), then 9.x. I wouldn't factory reset anymore of those older 79xx's. Here is a reference:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/7900_series/firmware/9_3_1SR1/release_notes/P790_BK_R4E1E768_00_rn-9_3_1_sr1-7900-series/P790_BK_R4E1E768_00_rn-9_3_1_sr1-7900-series_chapter_00.html#CUIP_TP_S3B5C8CB_00">
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/7900_series/firmware/9_3_1SR1/release_notes/P790_BK_R4E1E768_00_rn-9_3_1_sr1-7900-series/P790_BK_R4E1E768_00_rn-9_3_1_sr1-7900-series_chapter_00.html#CUIP_TP_S3B5C8CB_00</a></p>
<p>Prior to the cluster reboot (reboot would have been required (but not forced) since you were adding model support not previously supported) you mention that you did change the 7941 device default back to the 9.3(1) load; however, it seems the 7941 phones
may have gotten the prompt to upgrade. The 7941 should be able to upgrade from 9.3(1) to 9.4(2)SR1.1 (what would have been in that device pack) without issue however. Just for clarification, you did install the device pack on all cluster nodes, correct? If
you haven't rebooted the cluster yet, I'd suggest at least restarting the tftp services, then reboot in a maintenance window.<br>
</p>
<p>Thanks,</p>
<p>Ryan</p>
<br>
<div class="moz-cite-prefix">On 06/30/2016 10:05 AM, <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:george.hendrix@caci.com">
</a><a class="moz-txt-link-abbreviated" href="mailto:george.hendrix@caci.com">george.hendrix@caci.com</a> wrote:<br>
</div>
<blockquote cite="mid:255F57BB43F894468DA6BD4F2F5DD1CEE9DE157F@rw-s-exch03.net.its.l-3com.com" type="cite">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
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 class="WordSection1">
<p class="MsoNormal">Hey Guys,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Installed cmterm-devicepack9.1.2.15130-1.cop.sgn on CUCM 9.1.2.10000-28 cluster to enable support for 8841 phones. Now, I have a location where about 20 out of 30 7941 phones are not registering and getting TFTP timeout. The rest of
the phones are registered without issue. The phones were all registered fine with firmware SCCP41.9-31SR2-1S. I actually configured CUCM to keep this as the primary load so they would not attempt an upgrade immediately. We did a factory reset on one phone,
but now it’s stuck in upgrading loop and when I do show CDP neighbor, it shows 79XX_default_load. Both the phones that we have reset and the ones not registering can’t be pinged at all from outside the LAN. I can ping them all from the local switch, but
not from the neighbor router. However, I can ping all other phones in that VLAN.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thoughts?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Bill Hendrix | Network/VoIP Engineer<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset> <br>
<pre wrap="">_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset> <br>
<pre wrap="">_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>