<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
cmterm-7911_7906-sccp.8-3-4SR1.cop.sgn should do you well.<br>
<br>
This is all kind of assuming that there is a device in the path
performing SCCP inspection. Have you had any luck confirming that?<br>
<br>
/Wes<br>
<br>
On Monday, July 12, 2010 4:02:13 PM, STEVEN CASPER
<a class="moz-txt-link-rfc2396E" href="mailto:SCASPER@mtb.com"><SCASPER@mtb.com></a> wrote:<br>
<blockquote cite="mid:4C3B3C85.9874.0039.0@mtb.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<meta content="MSHTML 6.00.2900.3698" name="GENERATOR">
<div>Ugh....I should have caught that, I will load </div>
<div> </div>
<div>
<table sizset="76" sizcache="1" border="0" cellpadding="0"
cellspacing="0" width="100%">
<tbody sizset="76" sizcache="1">
<form name="viewFeatureForm"
onsubmit="return callImgFeatAction('relVer=8.3(4)_SR1&mdfid=280136569&sftType=Skinny+Client+Control+Protocol+(SCCP)+Software&optPlat=&nodecount=21&edesignator=null&modelName=Cisco+Unified+IP+Phone+7911G&treeMdfId=278875240&modifmdfid=&imname=&treeName=Voice+and+Unified+Communications&hybrid=Y&imst=N');"
method="post" sizset="76" sizcache="1">
<tr>
<td colspan="3">
<table border="0" width="100%">
<tbody>
<tr>
<td class="td-content-left" style="padding-right: 0px;"
width="85%">
<table class="table-columns" border="0" width="100%">
<tbody>
<tr>
<td class="td-content-left"
style="padding-right: 1px; white-space: nowrap;" colspan="2"
valign="top">cmterm-7911_7906-sccp.8-3-4SR1.cop.sgn <img
title="Login & Valid Contract Required"
alt="Login & Valid Contract Required"
src="cid:part1.00040708.01060306@cisco.com"> <br>
</td>
</tr>
<tr>
<td class="td-content-left" colspan="2"
valign="top">Release Date: 05/Mar/2008<br>
</td>
</tr>
<tr>
<td class="td-content-left" colspan="2"
valign="top">7911/7906 SCCP IP Phone load - Compatible CUCM Versions:
5.0(4)+<br>
</td>
</tr>
<tr>
<td class="td-content-left" colspan="2"
valign="top">
<div>Size: 3960.36 KB (4055403 bytes)</div>
<div> </div>
<div>or maybe </div>
<div> </div>
<div>
<table class="table-columns" border="0"
width="100%">
<tbody>
<tr>
<td class="td-content-left"
style="padding-right: 1px; white-space: nowrap;" colspan="2"
valign="top">cmterm-7911_7906-sccp.8-2-2SR4.cop.sgn <img
title="Login & Valid Contract Required"
alt="Login & Valid Contract Required"
src="cid:part1.00040708.01060306@cisco.com"> <br>
</td>
</tr>
<tr>
<td class="td-content-left" colspan="2"
valign="top">Release Date: 04/Jun/2007<br>
</td>
</tr>
<tr>
<td class="td-content-left" colspan="2"
valign="top">7911/7906 SCCP IP Phone load - Compatible CCM Versions:
5.0(4)+<br>
</td>
</tr>
<tr>
<td class="td-content-left" colspan="2"
valign="top">
<div>Size: 3670.78 KB (3758870 bytes)</div>
<div> </div>
<div>what do you think?</div>
<div> </div>
<div>Steve</div>
<br>
</td>
</tr>
</tbody>
</table>
</div>
<br>
</td>
</tr>
</tbody>
</table>
<br>
</td>
<td class="" align="right" valign="top" width="5%"><br>
</td>
</tr>
</tbody>
</table>
<br>
</td>
</tr>
<tr>
<td style="padding-left: 5px; padding-bottom: 5px;"
colspan="3">
<hr><br>
</td>
</tr>
</form>
</tbody>
</table>
<br>
<br>
>>> Wes Sisk <a class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a> 7/12/2010 3:51 PM
>>><br>
Nope, CM 5.1 and later all require signed files. You will need a
.cop.sgn for the installer to be recognized.<br>
<br>
/Wes<br>
<br>
On Monday, July 12, 2010 3:47:06 PM, STEVEN CASPER <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:SCASPER@mtb.com"><SCASPER@mtb.com></a> wrote:<br>
</div>
<blockquote cite="mid:4C3B38F9.9874.0039.0@mtb.com" type="cite">
<meta content="MSHTML 6.00.2900.3698" name="GENERATOR">
<div>Did the scan, I do not have any old enough firmware on my TFTP
servers. Can I install this on a CUCM 7.1.5.11900-6? </div>
<div> </div>
<div>
<table class="table-columns" border="0" width="100%">
<tbody>
<tr>
<td class="td-content-left"
style="padding-right: 1px; white-space: nowrap;" colspan="2"
valign="top">cmterm-7911_7906-sccp.8-3-4SR1.cop <img
title="Login & Valid Contract Required"
alt="Login & Valid Contract Required"
src="cid:part3.03040605.03030206@cisco.com"> </td>
</tr>
<tr>
<td class="td-content-left" colspan="2" valign="top">Release
Date: 05/Mar/2008</td>
</tr>
<tr>
<td class="td-content-left" colspan="2" valign="top">7911/7906
SCCP IP Phone load - Compatible CUCM Versions: 5.0(1), 5.0(2), 5.0(3)</td>
</tr>
<tr>
<td class="td-content-left" colspan="2" valign="top">
<div>Size: 3959.95 KB (4054987 bytes)</div>
<div> </div>
<div>Steve</div>
</td>
</tr>
</tbody>
</table>
<br>
<br>
>>> Wes Sisk <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a>
7/12/2010 2:41 PM >>><br>
I believe 7911 fits into the category of "3rd Gen Phone loads 8.3 and
earlier use SCCPv15 and earlier so will not be directly affected" so
you will need something even older than 8.5.3. The older loads should
be on the server as they should have migrated forward with other TFTP
files. To confirm what is available in TFTP from CLI:<br>
<br>
<tt>admin:file list tftp SCCP*<br>
SCCP11.9-0-2SR1S.loads SCCP31.9-0-2SR1S.loads<br>
SCCP41.9-0-2SR1S.loads SCCP42.9-0-2SR1S.loads<br>
SCCP45.9-0-2SR1S.loads SCCP6901.9-0-2-0.loads<br>
SCCP6911.9-0-2-0.loads SCCP69xx.8-5-2-70-7.loads<br>
SCCP69xx.8-5-2-70-7.zz SCCP69xx.9-0-2-0.loads<br>
SCCP69xx.9-0-2-0.zz.sgn SCCP70.9-0-2SR1S.loads<br>
SCCP75.9-0-2SR1S.loads <br>
dir count = 0, file count = 13<br>
</tt><br>
/Wes<br>
<br>
On Monday, July 12, 2010 11:52:29 AM, STEVEN CASPER <a
class="moz-txt-link-rfc2396E" href="mailto:SCASPER@mtb.com"
moz-do-not-send="true"><SCASPER@mtb.com></a> wrote:<br>
</div>
<blockquote cite="mid:4C3B01FD.9874.0039.0@mtb.com" type="cite">
<meta content="MSHTML 6.00.2900.3698" name="GENERATOR">
<style><!--
/* Font Definitions */
@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;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 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;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style>
<div>Thanks for this! I am going to try a preSCCPv17 version.
Would 8-5-3.for 7911_7906 already be on my 7.1.5 servers or would this
need to be downloaded and installed?</div>
<div> </div>
<div>Steve</div>
<div> </div>
<br>
<br>
>>> "Jason Aarons (US)" <a class="moz-txt-link-rfc2396E"
href="mailto:jason.aarons@us.didata.com" moz-do-not-send="true"><jason.aarons@us.didata.com></a>
7/12/2010 11:02 AM >>><br>
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125); font-family: 'Calibri','sans-serif';">SCCP
and fixup<O:P></O:P></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125); font-family: 'Calibri','sans-serif';"><a
class="moz-txt-link-freetext"
href="https://supportforums.cisco.com/docs/DOC-8131;jsessionid=92A3673D1CCD27D1388811BBD2AFDBDB.node0"
moz-do-not-send="true">https://supportforums.cisco.com/docs/DOC-8131;jsessionid=92A3673D1CCD27D1388811BBD2AFDBDB.node0</a><O:P></O:P></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125); font-family: 'Calibri','sans-serif';"><O:P></O:P></span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><b><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">From:</span></b><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';"> Jason
Aarons (US) <br>
<b>Sent:</b> Monday, July 12, 2010 11:00 AM<br>
<b>To:</b> 'STEVEN CASPER'; cisco-voip<br>
<b>Subject:</b> RE: [cisco-voip] 7911s not working after upgrade<O:P></O:P></span></p>
</div>
</div>
<p class="MsoNormal"><O:P></O:P></p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125); font-family: 'Calibri','sans-serif';">SCCP
Version number with firewall? Is firewall doing SCCP fixup?<O:P></O:P></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125); font-family: 'Calibri','sans-serif';">Google
sccp version number, Ryan or Wes have posted about fixup before.<O:P></O:P></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125); font-family: 'Calibri','sans-serif';"><O:P></O:P></span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><b><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">From:</span></b><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';"> <a
class="moz-txt-link-abbreviated"
href="mailto:cisco-voip-bounces@puck.nether.net" moz-do-not-send="true">cisco-voip-bounces@puck.nether.net</a>
[<a class="moz-txt-link-freetext"
href="mailto:cisco-voip-bounces@puck.nether.net" moz-do-not-send="true">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>STEVEN CASPER<br>
<b>Sent:</b> Monday, July 12, 2010 10:33 AM<br>
<b>To:</b> cisco-voip<br>
<b>Subject:</b> [cisco-voip] 7911s not working after upgrade<O:P></O:P></span></p>
</div>
</div>
<p class="MsoNormal"><O:P></O:P></p>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';"> We
upgraded from 6.1.3b to 7.1.5.11900-6 over the weekend. We have<br>
several sites in India where the 7911 telephones are not working now.
They have dial tone<br>
but when they call out they get a "UCM down" message. When we call them
on cluster the<br>
phone rings and when they answer we get a "temp fail" message. At the
same sites we have 7940 and 7941 that are working. These phones are all
behind a firewall. 7911 phones in the United States that are not behind
a firewall are working fine. <O:P></O:P></span></p>
</div>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';"><O:P></O:P></span></p>
</div>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">Opened a
TAC case and I am downgrading the firmware on one of the 7911s to see
if that makes a difference. Wondering if anyone has any thoughts?<O:P></O:P></span></p>
</div>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';"><O:P></O:P></span></p>
</div>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">Thanks,<O:P></O:P></span></p>
</div>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">Steve<O:P></O:P></span></p>
</div>
<pre>************************************<O:P></O:P></pre>
<pre>This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.<O:P></O:P></pre>
<pre>There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.<O:P></O:P></pre>
<pre>************************************<O:P></O:P></pre>
</div>
<hr size="1">
<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>
<pre>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</pre>
<pre wrap=""><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net" moz-do-not-send="true">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
<pre>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</pre>
</blockquote>
<br>
<pre>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</pre>
</blockquote>
<br>
</body>
</html>