Can you or can you not provision/upgrade ATA 186's via TFTP using CCM 3.1.3(a)?
I have over 100 ATA's to get upgraded to image version 2.15ms, and I don't want to have to do them manually (call me crazy!). All of them right now have a 2.15.bl bootload image on them, and I need to get rid of that.
This is what I can do:
If I create my binary file called ATAxxxxxxxxxxxx, it will take my other settings, but it will not upgrade the image. I have come to the conclusion that either I'm not setting something correctly in that file, or that it's just not possible to upgrade the ATA boxes using TFTP in my version of CallManager (maybe something to do with the fact that 3.1 has to have them in as 7960 phones?).
I opened up a TAC case regarding this issue, and the tech immediately told me to upgrade to 3.2, which (to me) doesn't seem like much of a solution, since we have 700 IP phones and 200 VGC phones that work nicely with 3.1. Although I understand that in 3.2 you can insert an ATA as an ATA 186 phone, there must be some way of getting it to provision successfully with 3.1.
I have run the prserv.exe utility, and see the ATA receive the binary file successfully, but for the life of me, it won't upgrade its image (the image is sitting in the TFTP directory on the TFTP server, and the binary file points to it).
In the sniffer, it only successfully registers with CCM if it uses the SEPxxxxxxxxxxxx.cnf.xml file. Even if I create an ATAxxxxxxxxxxxx.cnf.xml file, or the atadefault.cnf.xml file, the ATA will take it, but I get DB Config errors and it will not upgrade the image (see output below). I'm thinking here that if there is an ATAxxxxxxxxxxx.cnf.xml file, it wants to register with CCM as an ATA, which I can't do in my version.
Wed Jan 08 10:07:17 2003 Hello from firstname.lastname@example.org (0-1)
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...
[toc:faq]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 discusse...