Just upgraded our cluster to 220.127.116.11900-3 and now a new ATA 186 won't register with CCM. Tried another brand new one to no avail. It would get an IP address that is pingable but won't allow web access to it with an error "Invalid access". Hooked up a working ATA to the same jack and it came up just fine. I suspect both ATA have some outdate firmware but do not know how to get over this issue.
Any help would be greatly appreciated.
OK, then you're going to have to download the 3.2.4 firmware from CCO, then TFTP the ATA.cnf.xml file from your current call manager to your PC, modify the ATA.cnf.xml file so that it's less than 4K in size...change the configuration in the file to reflect ATA030204SCCP090202A.zup firmware. Then configure the ATA manually using an analog phone to change the TFTP server to your PC's IP address, put the new .cnf.xml file in your TFTP root, start up your TFTP sever on your PC and let the ATA upgrade to 3.2.4.
After this is done, manually change the ATA TFTP address back to CUCM, and let it re-register using the hosted .cnf.xml file.
Directions for pulling a file down from CUCM to your PC using TFTP via windows cmd prompt:
tftp get ATA.cnf.xml ATA.cnf.xml
Here's a guide on how to manually configure the ATA using a connected analog phone:
If you have any issues feel free to open a TAC case.