<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[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>
<!--
/* 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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-believe-normal-left:yes;}
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<![if mso 9]>
<style>
p.MsoNormal
{margin-left:3.0pt;}
</style>
<![endif]><!--[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]-->
</head>
<body lang=EN-US link=blue vlink=purple style='margin-left:3.0pt;margin-top:
3.0pt;margin-right:3.0pt;margin-bottom:.75pt'>
<div class=Section1>
<p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:3.0pt;
margin-bottom:5.0pt;margin-left:3.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>8.3(2) can not be upgraded to
8-5-2SR1S . they can however be upgraded to 8-5-2S. Upgrade them first to
8-5-2S and then 8-5-2SR1S.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:3.0pt;
margin-bottom:5.0pt;margin-left:3.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Reference for 8.5(2)<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:3.0pt;
margin-bottom:5.0pt;margin-left:3.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><a
href="http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_2/english/release/notes/7900_852SR1.html">http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_2/english/release/notes/7900_852SR1.html</a><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:3.0pt;
margin-bottom:5.0pt;margin-left:3.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>For all SCCP firmware upgrades
from firmware release versions earlier than 8.3(3) to version 8.5(2)SR1 or
greater, you must first upgrade your firmware to version 8.5(2). Once you have
upgraded to version 8.5(2), you can upgrade your IP Phone to version 8.5(2)SR1
or later.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:3.0pt;
margin-bottom:5.0pt;margin-left:3.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:3.0pt;
margin-bottom:5.0pt;margin-left:3.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Reference for 8.5(3) (future)<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:3.0pt;
margin-bottom:5.0pt;margin-left:3.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><a
href="http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_3/english/release/notes/7900_853.html">http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_3/english/release/notes/7900_853.html</a><o:p></o:p></span></p>
<p class=MsoNormal style='margin-right:3.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>For all SCCP firmware
upgrades from firmware release versions earlier than 8.3(3) to version 8.5(3)
or greater, you must first upgrade your firmware to version 8.5(2). Once you
have upgraded to version 8.5(2), you can upgrade your IP Phone to version
8.5(3) or later<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Jason Aarons (US)<br>
<b>Sent:</b> Tuesday, October 06, 2009 7:09 PM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] 7962 Registration Issues with 7.1.2.32014-1 ?<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div id=idOWAReplyText11921>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D'>We are
</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> building
<span style='color:#1F497D'>new out of box </span>7962's<span style='color:
#1F497D'> come from factory running </span></span>8.3(2) <span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> and <span
style='color:#1F497D'>are </span>having registration issues with your 7962<span
style='color:#1F497D'>/7915s. Our production CallManager is running
7.1.2.32014-1 and the Device Defaults for 7962 are SCCP42.8-5-2SR1S</span><o:p></o:p></span></p>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>When the 7962's
initially boot and go out to load the firmware, it will immeidately get an
"auth fail". <span style='color:#1F497D'>We are using SCCP
Non-Secure Mode. </span>In some instances, the phone will fail to load
the firmware but will still register however not many of the functions will
work. I've seen one instance where the phone actually came up with the
right configuration yet, in Call manager it didn't even show registered.
The status was "unknown".<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>What we did earlier
this morning was pointed <span style='color:#1F497D'>a test</span> 7962 to <span
style='color:#1F497D'>another 7.1(2) cluster and</span> let the phone
auto-register and pull the correct load. Once the phone came back up and
auto-registered to the <span style='color:#1F497D'>other </span>cluster<span
style='color:#1F497D'> then </span>we just reset the phone dhcp settings to
enabled so that the phones would re-register back to the <span
style='color:#1F497D'>first </span>cluster. Once we did this then the
phones would be able to register fine to the <span style='color:#1F497D'>original
cluster.</span><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Under the
phone configuration in the device information box, the "Active Load
ID" will be unknown. When you see this you will either have problems
with the 7962 coming up properly issues with the Sidecar if you have a sidecar.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
</div>
<div class=MsoNormal align=center style='margin:0in;margin-bottom:.0001pt;
text-align:center'>
<hr size=1 width="100%" align=center>
</div>
<p><strong>Disclaimer: This e-mail communication and any attachments may
contain confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the intended
addressee, you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you. </strong><o:p></o:p></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>