<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: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)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>When we upgraded Call Manager, none of our ATAs upgraded, we
ended up doing them manually .<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 style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><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>Mike King<br>
<b>Sent:</b> 26 April 2010 14:48<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] CUCM 7.1(3a) ATA Box rejected<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I can confirm that. I had over 20 ATA's that were
registered, but not upgrading.<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I didn't think of the Modified Device Pool, I'll have to try
that (I still have a few ATA's that I have to upgrade)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The method I was using was to setup a TFTP server on my
laptop. Copy the .zup file, and the xmldefault.cnf.xml to the TFTP
root folder. I edited the xmldefaul file to only have a couple lines in
it. (get it below the 4K limit (mine was around 6k). Changed the
Default TFTP server from the ATA's Web-interface to my Laptop,and let it
upgrade. When it was finished, change the default server back. It
works, but it's not as elegant as the Modified device pool.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Mike<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>On Thu, Apr 22, 2010 at 4:28 PM, Ryan Ratliff <<a
href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal>Most devices will default to registering with their
configured TFTP server even if they cannot get a TFTP configuration file.
This is the case with ATAs, and I believe you will find that they are
registered with their TFTP server now.<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>In this case it really isn't the ATAs not getting the config
file, it's them failing to parse it because of the size. If they aren't
upgrading, they either aren't getting the config file or they aren't parsing
it.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#888888'><o:p> </o:p></span></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'>-Ryan<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>On Apr 22, 2010, at 4:19 PM, Reto Gassmann wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>Hi Ryan<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I asume, that if the ATA is registered in the CUCM 7, the
configuration file is not bigger than the 4k. And even then, the ATA does not
get updated to the newest load. No ATA box on the CUCM 7 cluster gets updated
to the newest load. If I try the same on the CM 4.3 cluster, the ATAs are
updated without any problem.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Reto<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>2010/4/22 Ryan Ratliff <<a
href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>><o:p></o:p></p>
<div>
<p class=MsoNormal>If the ATA's tftp configuration file is bigger than 4k on
the 7.x CUCM server then you are hitting the very bug that has been the focus
of this thread (and others). <o:p></o:p></p>
<div>
<p class=MsoNormal><span style='color:#888888'><o:p> </o:p></span></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'>-Ryan<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>On Apr 22, 2010, at 7:38 AM, Reto Gassmann wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>Hallo Ryan<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I tried the fix you described in your mail. It
works fine as far as the point where the ATA should be updated from the
CUCM 7. In our CM 4.2 environment the ATA box gets updated from
Version 030203 to 030204 immediately when I change the phone load file in
ccmadmin and restart the ATA box. If I try the same on a 7.1(3a) CUCM,
the ATA box gets no update. Is this a known bug?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Reto<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>2010/4/14 Ryan Ratliff <<a
href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>><o:p></o:p></p>
<p class=MsoNormal>The issue was with the size of the configuration file and a
4k limit the ATAs had. Typically the ATA will fail to parse the file if
it's too large, and just try to register with the configured TFTP server.
If the TFTP server isn't in the CM group for the ATA this could cause the
registration to get rejected.<br>
<br>
The easiest way to try and workaround this is to create a device pool with a CM
group with only a single server in it, and as minimal of a configuration as you
can make it. This will hopefully drop the config file down below 4k and
let the ATA upgrade to the newer load. At that point you can move it back
to the normal device pool and it will be fine.<br>
<br>
-Ryan<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
On Apr 13, 2010, at 11:03 AM, Robert Kulagowski wrote:<br>
<br>
>> we plan the upgrade of our Callmanager Cluster from 4.2(3) to 7.1(3a).<br>
>> We have some ATA Boxes attached to the CallManager. We tried the
upgrade in<br>
>> our lab and found out, that most of the ATA Boxes updatetd itself
fine.<br>
>> However one Box appears as "Rejected" in the ccmadmin Device
Pages. I did a<br>
>> factory reset, but the ATA box is still rejected.<br>
>><br>
>> Has anyone an idea why? Other ATA Boxes with the same HW typ are up
and<br>
>> running.<br>
><br>
> Have you checked the archives of this list? I'm pretty sure that<br>
> you'll see that there's an issue with the firmware of the ATA needing<br>
> to be on 3.2.4 _before_ the upgrade to 7.1.3(a).<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'>>
_______________________________________________<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/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<p>
<p>------------------------------------------------------------------------------------------------------------<p>
<p><font color="green"><span
style='font-size:14.0pt;font-family:Webdings;mso-bidi-font-family:Webdings;
color:green'>P<b> </b></span>Reduce your environmental footprint, please don't print this e-mail unless you really need to.</font>
<p>The information in this message including any attachments may be confidential or privileged and is for the use of the named recipient only. If you are not the named or intended recipient you may not copy, distribute, or deliver this message to anyone or take any action in reliance on it. If you receive this message in error please contact the sender immediately and delete it from your system
<p>
<p>Scanned by Anti Virus Software<p>
</body>
</html>