[cisco-voip] CUCM 7.1(3a) ATA Box rejected

Mon Apr 26 09:54:30 EDT 2010

When we upgraded Call Manager, none of our ATAs upgraded, we ended up
doing them manually .

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike King
Sent: 26 April 2010 14:48
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 7.1(3a) ATA Box rejected

I can confirm that.  I had over 20 ATA's that were registered, but not
upgrading.

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)

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.

Mike

On Thu, Apr 22, 2010 at 4:28 PM, Ryan Ratliff <rratliff at cisco.com>
wrote:

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.

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.

-Ryan

On Apr 22, 2010, at 4:19 PM, Reto Gassmann wrote:

Hi Ryan

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.

Reto

2010/4/22 Ryan Ratliff <rratliff at cisco.com>

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).   

-Ryan

On Apr 22, 2010, at 7:38 AM, Reto Gassmann wrote:

Hallo Ryan

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?

Reto

2010/4/14 Ryan Ratliff <rratliff at cisco.com>

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.

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.

-Ryan

On Apr 13, 2010, at 11:03 AM, Robert Kulagowski wrote:

>> we plan the upgrade of our Callmanager Cluster from 4.2(3) to
7.1(3a).
>> We have some ATA Boxes attached to the CallManager. We tried the
upgrade in
>> our lab and found out, that most of the ATA Boxes updatetd itself
fine.
>> However one Box appears as "Rejected" in the ccmadmin Device Pages. I
did a
>> factory reset, but the ATA box is still rejected.
>>
>> Has anyone an idea why? Other ATA Boxes with the same HW typ are up
and
>> running.
>
> Have you checked the archives of this list?  I'm pretty sure that
> you'll see that there's an issue with the firmware of the ATA needing
> to be on 3.2.4 _before_ the upgrade to 7.1.3(a).

> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

------------------------------------------------------------------------------------------------------------ 
Reduce your environmental footprint, please don't print this e-mail unless you really need to.

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

Scanned by Anti Virus Software
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100426/79db6d7f/attachment.html>