<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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.<div><br></div><div>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.</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>-Ryan</div></span>
</div>
<br><div><div>On Apr 22, 2010, at 4:19 PM, Reto Gassmann wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Ryan</div>
<div>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.</div>
<div> </div>
<div>Reto<br><br></div>
<div class="gmail_quote">2010/4/22 Ryan Ratliff <span dir="ltr"><<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div style="WORD-WRAP: break-word">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).
<div><br><font color="#888888">
<div><span style="TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: normal; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px">
<div>-Ryan</div></span></div></font>
<div>
<div></div>
<div class="h5"><br>
<div>
<div>On Apr 22, 2010, at 7:38 AM, Reto Gassmann wrote:</div><br>
<blockquote type="cite">
<div>Hallo Ryan</div>
<div> </div>
<div>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?</div>
<div> </div>
<div>Reto<br><br></div>
<div class="gmail_quote">2010/4/14 Ryan Ratliff <span dir="ltr"><<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">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<br>
<div>
<div></div>
<div><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).<br></div></div>> _______________________________________________<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><br><br></blockquote></div><br></blockquote></div><br></div></div></div></div></blockquote>
</div><br>
</blockquote></div><br></div></body></html>