Why we need to upgrade ATA 186 manually?
ATA 186 running on firmware less than 3.2.4 has a limitation, by which it cannot download a configuration file greater than 4Kb in size.
This has been reported under the Bug: CSCsd44357
Note: The bug talks about only the XMLDefault.cnf.xml file, but it valid for any configuration file which is present for any ATA 186 on the CUCM TFTP server which is larger than 4kb
CUCM versions 8.x and further has XMLDefault.cnf.xml greater than 4kb, and even we do manual configuration, the file size still exceeds 4kb.
So, If we are migrating our cluster from any version lesser than 8.x to 8.x or higher, we want to make sure that we need to upgrade the firmware of ATA 186 with the existing CUCM version( lesser than 8.x) by uploading the firmware 3.2.4 to CUCM TFTP and let the ATAs download the firmware and upgrade it before the migration.
In case somebody has upgraded the cluster but forgot to upgrade it and the previous CUCM servers are not available, then we follow the following 2 technique to upgrade the ATA 186 firmware manually to 3.2.4 and let the phone register to new CUCM.
Method 1: Using sata186su.exe utility
Step 1 : Download the “ata_03_02_04_sccp_090202_a.zip” from the CCO page for the ATA 186 to any PC which is reachable to ATA 186 on layer 3.
Step 2: Extract the above .zip file in a folder.
Step 3: Copy ATA030204SCCP090202A.zup and sata186us.exe files and put it in a separate folder.
Step 4: Open CMD utility on the desktop and navigate your path to the folder in which you have copied the files in the above step and run the command “sata186us ATA030204SCCP090202A.zup -d1 -any2.
After you run the above command the screen will look something like the following:
Step 5: Connect you ATA 186 to network and let it boots up. Don’t’ worry if it does not register with you new CUCM and show “unknown” “unknown” in the CUCM.
Step 6: Once the ATA has been booted, press the red button on the top, it takes you to the main menu.
Step 7: Now, Dial the code displayed in the cmd screen above ( this is going to be different in your case), 100#10*82*247*169*8000#
Step 8: The ATA will upgrade the firmware and the voice over will prompt you with “the upgrade has been successful”.
Step 9: Unplug the network cable from the ATA and plug it back. ATA will reload and will download the configuration file and will register fine to the new CUCM cluster.
Note: If you are using DHCP, make sure that you take a note of the IP address of the ATA by using the codes mention in the “Basic configuration guide for ATA 186”. You may want to open “https:\\<IP Address>\dev” for the ATA and check the ATA details
Method 2: Trimming XMLDefault.cnf.xml.
Step 1: Download XMLDefault.cnf.xml file from the CUCM TFTP server. It is a larger file more than 4kb. This is due to the presence of all the phones Firmware in the file. It looks like from inside.
Note: To download the file, use ‘cmd’ of windows and run the command “tftp -i <IP Address of TFTP> get SEP<MAC address>.cnf.xml”
Step 2: Trim the file by deleting all firmware information except ATA 186 and save it. It will make the file less than 4kb. Please see below:
Note: When you download the file from the CUCM TFTP server using step 1, it downloads the file in “Read Mode” only. Right click on the file, go to properties and uncheck the “read only” option and save it. Now you make the modifications.
Step 3: Put the configuration file and the firmware in a separate folder.
Step 4: Use and 3rd party TFTP utility, make the root directory as the one we created in step 3.
Step 5: Change the option 150 in the DHCP server for the ATA to IP address of the PC where you are running 3rd party TFTP.
Step 6: Unplug the network cable from the ATA and plug it back.
Step 7: Since we have changed the TFTP server settings in the option 150 of DHCP, now ATA will request the configuration file from the TFTP that we have set-up above.
Step 8: ATA will successfully download the file configuration file and will upgrade the new firmware and will register to CUCM.
##Attaching the full and the trimmed XMLDefault.cnf.xml from CUCM 10.5.1
