ATA 186s registering with Publisher instead of Subscribers

cpoper · ‎04-27-2010

Hi everyone,

I have a question regarding a new batch of ATAs that we recently received. These ATAs register with the Publisher instead of any of the Subscribers (we have 3 Subscribers).

These ATAs show as Version: v3.1.0 atasccp (Build 040305B). I've tried changing the Device pool, but they are correct as the CM groups do not include registering to the Publisher, only to Subscribers. I'd like to have the ATAs register to a Subscriber

Older ATAs register properly to Subscribers, their version lists as 3.02.03(051201A). Furthermore, I can browse to the ATA IP Addresses whereas on these new ones, I receive an "Invalid Access" error and must browse to IP Address followed by /dev

Has anyone ever encountered this type of situation?

Thank you for your time.

Mac_Aodha · ‎10-07-2010

Did you ever find a solution for this? I have just discovered that I'm having the exact same problem.

Felipe Garrido · ‎10-08-2010

What version of CUCM is in use? Are you sure that the DHCP server has the correct TFTP server (Option 150) configured? Are you using the Pub as the lone TFTP server?

The best thing to do would be to get a packet capture of the registration process to determine if the ATA tries to register to the SUBs and fails.

On older ATA firmware, to access the web page, the address is http://

The newer versions, possibly starting with 3.2, use http:///

-Felipe

subash cobi · ‎11-02-2011

Hi,

Have anyone found the solution for this.

I have the same issue. My ATA 186 are registering to the PUB instead of the SUB.

All phones in the same device pool and using the same DHCP registers to the SUB.

Anyone can help,

Thanks.

Karthik Sivaram · ‎11-04-2011

hi Subash,

It may be caused due to CSCsd44357. The fix is available in the latest release of the firmware .

Hope this helps!

Thanks,

Karthik

subash cobi · ‎11-04-2011

hi Karthik,

You were right i was due to the 4k size bug.

Got it reslove using this solution:

https://supportforums.cisco.com/message/3481255#3481255

Thanks.