12-09-2015 01:14 AM - edited 03-17-2019 05:09 AM
Hi all,
firstly thanks for reading this post.
I have a Cisco ATA 190 that can't register with CUCM. This is a new deployment and is the first time an ATA 190 will register with CUCM. I've added the software to CUCM, both the "cmterm-ata190-qed.1-2-1-004.k3.cop.sgn" and "cmterm-ata190.1-2-1-004.k3.cop.sgn". As all the TFTP server details and IP's are correct (as verified on the WebGUI) I have been advised I have to upgrade the firmware to 1.2.1 on the ATA. However in the WebGUI there is no option to upgrade the firmware. does anyone have any idea how to do this?
PS since adding the new software I haven't rebooted CUCM, do I need to do this?
thanks
Dave
12-09-2015 02:05 AM
*IF* your CUCM already had support for the ATA190 and all you're doing is updating the default firmware, there's no need to reboot CUCM. All you need to potentially do is restart the TFTP process.
What version of firmware does the ATA currently have? If it has a very early version, you may be hitting BugID CSCur55187 (ATA Generates wrong name for CUCM server) or BugID CSCur55187 (CDP not enabled by default)
GTG
12-09-2015 02:33 PM
Hi Gordon,
I'm sure it never had support for the 190.
The current version of firmware is 1.1.2.
Rgds
Dave
12-13-2015 09:21 PM
So if CUCM didn't have the ATA190 as a device do I have to reboot all CUCM Servers, both Publisher and all subscribers? What about TFTP servers?
12-14-2015 12:27 AM
If the ATA 190 device type isn't listed in CCMadmin...
...then you have to apply a device pack to add support for the device.
When you install a device pack to add support for a new device, you have to perform a cluster reboot* for the change to take effect.
GTG
*You can cheat, and "only" restart the CallManager, TFTP & Tomcat processes on each server.
12-17-2015 06:11 PM
Hi Gordon,
the device is there. I've already added it into CUCM and it doesn't register.
Hence why I thought I needed to maybe manually upgrade the ATA to get it to work.
thanks
Dave
12-21-2015 03:03 AM
Maybe try Wiresharking the ATA to see if you can infer what's going wrong.
GTG
12-22-2015 01:03 AM
Hi Gordon,
the capture has shown FCS errors when the .cnf.xml file is being downloaded from the TFTP server when requested from the ATA. Once the FCS errors are finished the ATA trys to download other files which I'm sure are there just as a backup if the first file isn't there....such as....
CTLSEPMAC.tlv
ATAMAC01.cnf.xml
XMLdefault.cnf.xml
I loaded a TFTP client and I can get ATAMAC.cnf.xml from the TFTP server, yet the ATA clearly can't. My PC and the ATA are connected to the same switch.
Wierd.
12-22-2015 04:44 PM
there are no error's on the interfaces and the ATA is auto 100mb full duplex.
12-22-2015 06:14 PM
so I managed to upgrade the ATA to 1.2.1 using a hack.
It still doesn't register.
Here's the output from wireshark showing the registration issues. the Server IP is correct...
Here's the output from wireshark showing the FCS errors when it trys to download the file from TFTP server. The TFTP server's IP is correct...
01-14-2016 12:17 PM
hey,
were you able to get it registered? also wahts your cucm version?
I have the same problem on cucm 9.1.2. i haven't done wireshark to find out for fcs error. but it just wont register.
thanks
vijay
11-09-2023 03:50 AM
Hi, can you explain me which firmware file you used to upgrade the ATA?
I can't find a fw file in order to upgrade directly the ATA (not from cucm).
Regards
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide