I´ve recently migrated 3 branch offices of a customer who has a CCM cluster 6.1, and on everyone of them the model is the same: IP Phones and ATA186 to replace phones, a 2960 Poe and a Cisco 2801 to be DHCP server and SRST for phones, and GW to PSTN.
But on one branch office, the ATA186s didnt upgrade the firmware when register to CCM, and didnt get the SRST info. Them register to CCM cluster ok, and normally operate receiving and making calls. I had to manually upgrade the ATA186s, but the SRST config cant be corrected. It still says that the default router is the SRST and not the Cisco 2801. The ATA186s and IP Phones of that branch has the same device pool and srst config, but IP Phones did upgrade ok and has the right config for SRST.
I´ve checked replacing the ATA186, and it´s the same situation.
On the other two branch offices this situation didnt occurs, ATA186s upgrade normally and have the right SRST config.
It seems an issue with the WAN link, but if it´s the case, why IP Phones upgrade normally and gets SRST config ok?
Hi Andres, You may want to check the DHCP configuration and check if the option 150 is configured. If the ATA is successfully grabbing the TFTP IP Address, you want to make sure that the ATA is downloading the configuration file. The configuration file will have the information about the new firmware version and also the SRST information. If you are not sure that the ATA is downloading the config file, you can either collect sniffer trace or TFTP traces of the TFTP server (need to set to detailed level). I hope this help. Marcos
Hi Andres, If you verify that the ATA is downloading the configuration in the TFTP traces successfully, you can download the config file in your desktop and verify the content of the file to see if the SRST is listed there. In order to download the confg file, you basically need to install a TFTP client on your desktop and get the file from the TFTP Server. You should see the name of the file in the TFTP traces. It should be something like ATA+MAC Address.cnf.xml. I hope this helps. Marcos
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...