There was a bug that was fixed in the very latest release for the Cisco ATA186, where if the config file was over a certain size, it would be ignored. <div><br></div><div>I personally fixed this by:</div><div><ol><li>Add the new firmware to the CCM server (otherwise it will just downgrade when it registers)</li>
<li>copying the config file from the CCM server to my laptop. </li><li>Installing a TFTP server on my laptop. </li><li>Copy the config file, and the updated ATA firmware files to my laptop</li><li>Editing the config file to remove all the other phone types other than ATA. This was usually all I needed to shrink the Config file under the limit.</li>
<li>log into the web interface of the ATA</li><li>Set the TFTP server to the IP of my laptop</li><li>Powercycle the ATA</li><li>The ATA would upgrade</li><li>Log into the web interface of the ATA</li><li>Set the tftp server back to the default ( I believe it's either blank, or 0.0.0.0)</li>
</ol><div>Mike</div></div><div><br><div class="gmail_quote">On Fri, May 4, 2012 at 5:36 AM, Thierry De Vriendt <span dir="ltr"><<a href="mailto:thierry@autempspourmoi.be" target="_blank">thierry@autempspourmoi.be</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d">Hello,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d">We are currently moving some Cisco ATA 186 from our old CCM 4 to CUCM 8.6<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d">The ATAs use Skinny. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d">We have the following issues:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p style="margin-left:38.25pt"><u></u><span style="font-family:"Courier New";color:#1f497d"><span>1)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Courier New";color:#1f497d">If we change the option 150 (TFTP server) in the DHCP server to the new CUCM, it doesn’t work, the ATA still registers to the old CCM.<u></u><u></u></span></p>
<p style="margin-left:38.25pt"><u></u><span style="font-family:"Courier New";color:#1f497d"><span>2)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Courier New";color:#1f497d">Even after a restore to factory settings, the ATA still registers to the old CCM.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d">If we take ethereal traces, we can see the ATA requests his configuration file to the new CUCM and the TFTP server sends the file. Then the ATA sends a register message to the old CCM.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d">Does anybody have already experienced similar behavior?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d">Thanks.<span class="HOEnZb"><font color="#888888"><u></u><u></u></font></span></span></p>
<span class="HOEnZb"><font color="#888888"><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d">Thierry<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Courier New";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p></font></span></div></div><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><br>
<br></blockquote></div><br></div>