Old versions of CTS code (1.7 and earlier) could simply be uploaded as a .sbn file to CUCM via the web GUI. New versions (1.8 and beyond) are packaged as .cop.sgn files which need to be installed to CUCM via a CD/DVD or off an (S)FTP server. You can't simply upload the COP file to the FTP server as with the older .sbn files.
This upgrade guide was originally written for CTS endpoints, but it's the same procedure for TX and IX endpoints.
Stepwise Upgrades
If you upgrading to a CTS version above 1.7.4, a stepwise upgrade through 1.7.4 is recommended by the BU.
If you are upgrading to TX 6.0 on a TX-9000 series endpoint, a stepwise upgrade through 1.9.3 is required! This is because the old upgrade scripts do not parse for the new TX version numbers. If you do not do this stepwise upgrade you will see the following error in the sysop logs: "WARN Software downgrade denied for this CUCM device type"
For IX5000, you must go up to 8.0.3 before you can go to 8.1 and above.
Download the software
Download the .cop.sgn file for the version you want from CCO: http://www.cisco.com/cisco/software/navigator.html?mdfid=281201441&flowid=20562. You can verify the exact files for each firmware version in this document.
Set up an SFTP server on your local machine
You cannot upload the COP file to the TFTP server via the CUCM web interface, it has to be either burned to a disc or placed on an (S)FTP server. If you already have an FTP server you can use, put it on there. Otherwise the easiest way to get the file from your computer onto CUCM is setting up an SFTP server on your local machine.
The easiest server to set up is CoreFTP Mini SFTP Server (msftpsrvr.exe) but you can use whatever software you prefer. CoreFTP mini a free, portable application with very few options. You can download it here: http://www.coreftp.com/server/ - or via this direct link. This guide uses the free, portable server at the bottom of the page. If you downloaded an installer, you downloaded the wrong file.
Set up the SFTP server with the following options. Note that your username and password should be different or your might have issues.
User: [Any username]
Password: [Any password]
Port: 22
Root path: [Directory of the COP file]
Hit the "Start" button.
Install the COP file
Go to CUCM and get to OS administration
Then, Software Upgrades -> Install/Upgrade
Fill out the following in the Software Location form:
Source: Remote Filesystem
Directory: /
Server: [Your local machine's IP address]
Username: User configured in CoreFTP
Password: Password configured in CoreFTP
Transfer Protocol: SFTP
Select which file you want to install on the next screen. Note: If the file does not appear, try removing all other files but the .cop.sgn from the directory. Some files may "trip up" the CUCM and make it say there are no available upgrades.
The CUCM will take a minute to download the file. On the next screen you can compare the MD5 hash value of the uploaded file to the MD5 listed on CCO to make sure the download wasn't corrupt. Hit "Next". The file will begin to install; when you see "Successfully installed", you're done.
Afterwards we want to restart the TFTP Service on CUCM. Go to Serviceability.
Go to Tools -> Control Center - Feature Services
Select your CUCM server, then tick the box next to "Cisco tftp" (Under CM Services).
Hit the restart button at the top of the page.
Set the correct phone load
Go back to OS Administration. To double check that the file is installed, go to Software Upgrades -> TFTP File Management. Do a "contains" search for your software version, separated by dashes.
Look for the .loads file; this is what you will put under the "Phone Load Name" in the device profile. The last two characters of the name determine which codec the file is for:
P1: "CTS Series" CTS-CODEC-PRI-G2 or CTS-CODEC-PRIM (Ex. CTS-500-37, CTS-1300-65, CTS-3000)
P2: "TX Series" CTS-CODEC-PRI-G2R (Ex. CTS-500-32, TX-1300, TX-9000)
Copy the filename of the file you need (minus the ".loads" at the end) and put it under the CTS device profile in CUCM Administration:
Save and apply your configuration. After the endpoint reboots a couple of times (leave it for at least an hour), you should be up and running with the correct code. Do not forget to also upgrade your midlets if applicable.
Cisco.com Documentation:
