ATA 187 registering after power reset

ichehouri · ‎03-24-2011

Hi

i have CUCM cluster 8.0.3 working as centralized call processing and i have remote sites with IP phones (7911, 7942 and 7945) plus ATA 187 (version 9.0.3)

the phones are working fine but some ATAs are unregistering and will only register with power reset. Now i have more than 100 remote sites and in 20% of them i am facing this issue. Note that some sites are having 2 ATA and one have no issue while the other yes

i checked the network (it is working as 100 Full duplex) and no errors are there. I can also ping the ATA from CUCM during the issue and i can also browse it (it shows registering on the DNs). I also tried removing the ATA from CUCM server ans adding again but still same issue

did someone face such issue and what could be causing this

regards,

Ibrahim

ichehouri · ‎03-25-2011

Any suggestions please

caytos1989 · ‎03-25-2011

I have the exact same issues...I only have 20 remote sites, each with an ATA 187 for FAX and a wireless Analog Phones that keeps being Rejected by the Call Manager, and what i have to do is delete the phone from my CUCM, turn the port off on the switch, and then add the device manually, and turn the switchport on..

Ive been doing this every two o three days...NO ONE KNOWS HOW TO FIX IT!!!

Please help!

a.foerster · ‎03-26-2011

Hi Ibrahim,

we had the same issue at a customer of us. It finally turned out to be a firewall problem. There were two ASAs between the HQ and the remote site. Doing a packet capture on both sides we found out that packets from the ATA weren't arriving at the CUCM. It seemed like only the SIP Request packets with the identity of the ATA187 won't arrive at the CUCM. However, we didn't see any packet drops or ACL matches on any of the ASAs. From a configuration point of view, the traffic was completely allowed to pass but somehow still the ASAs influenced the communication. Since there were only 4 ATA 187, we exchanged them for a VG204 as a workaround.

Maybe you can do a packet capture, too to see if it is the same behaviour on your side.

Regards,

Andreas

ichehouri · ‎04-01-2011

Hi Andreas,

there were firewall in our situation but the issue not solved after turning it off. the only way to make the ata working it power reseting. we did packet capture before and after power reseting. attached is a copy.

ATA MAC: D0574C6BD7F1

ATA IP: 10.131.138.9

primary CUCM IP: 10.70.78.112

secondary CUCM IP: 10.128.60.21

ichehouri · ‎04-03-2011

Any ideas

regards,

Ibrahim

a.foerster · ‎04-04-2011

Hi Ibrahim,

what is IP address 10.150.30.38? Is this your PC? From this address HTTP requests get sent to the ATA.

Actually what I see in the traces is that you seem not to have correctly configured the ATA on CUCM. The ATA requests it's config file for port 2 which is ATA574C6BD7F101.cnf.xml. Please remember that the ATA has two ports that register with CUCM independently.
Now, CUCM responds that it cannot find this file, therefore the ATA downloads a "default config" that is mainly used for auto-registration.
Please change the MAC of the ATA in CUCM to 574C6BD7F101, save and click "apply" and check again if it works.

Regards,
Andreas

ichehouri · ‎04-04-2011

Hi,

yes 10.150.30.38 is my pc IP address. I was browsing the ATA remotly. The ATA is configured well (MAC: D0574C6BD7F) for port 1 but the 574C6BD7F101 is for the second port which iam not even configuring on the CUCM. if i configure the second port as 574C6BD7F101 it will also not register. if we do power reset for ata it will register

regards,

Ibrahim

a.foerster · ‎04-04-2011

Hi Ibrahim,

where is the capture from? Directly from the ATA or from the CUCM or anywhere inbetween?

Regards,

Andreas

ichehouri · ‎04-04-2011

we did port mirroring on the switch (the ATA port was the mirrored port) to a port where the sniffer in connected

regards,

Ibrahim

a.foerster · ‎04-04-2011

OK this is weird. Because I thought maybe the capture was from a point inbetween where we don't see all packets from the ATA. In the capture before the reboot, the only thing it does is requesting the config for the second port. There is only TFTP traffic and nothing else. So it doesn't register because the ATA doesn't send any register requests. Normally it should continue to do so all times. So this seems to be be definitely some kind of bug. Do you have the most current firmware on it? If not, please do an update. If yes, I'm afraid only Cisco can help any further. :-(

Regards,

Andreas

ichehouri · ‎04-04-2011

Yes Andreas it is weird. i do not know why there is no register request. We already have the latest release on the ATA. I opened TAC case with Cisco from one week and not solved yet.

regards,

Ibrahim

j.huizinga · ‎04-23-2011

The ATA187 is an awfull device. We have a lot of issues with it.

The device get's unregistred or rejected by itself, and the only way to make it work again is to power cycle the thing.

After that it works for some time (days or weeks)

Missing the good old days of the ATA186

JH

d.haeni · ‎05-08-2012

We're dealing with a similar issue. I thought this bug might match:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtq85079&from=summary

ATA187 will crash if port2 keeps tftp downloading
Symptom: ATA-187 will crash if port 2 keeps tftp downloading Conditions: Port 2 does not have DN configured. Workaround: Configure DN on port 2

Cheers

/David

Youssef Aoufi · ‎02-21-2012

Hi all,

Did you find a solution for this problem?

I am facing the exact same issue with one of our customers.

Thank you in advance