When you don't find the IP Phone model listed in the Device defaults you can either install the required Device Pack (which adds the Firmware as well) or upgrade to a supported later CCM Version. Here is the minimum required device Pack for the 7945,7965 and 7975 and CCM 6.0
Note: Cisco recommends that you apply this Device Package during a maintenance window.
NOTE: Apply this patch to all of your Cisco Unified CallManager servers, beginning with the publisher server and TFTP server.
When applying this Device Package to enable new device support, a cluster-wide reboot is required for those devices to register successfully. A clusterwide reboot IS NOT required when running to update existing firmware/support.
For Cisco Unified CallManager 6.0, you must do all software installations and upgrades by using the Software Upgrades menu options. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified CallManager with Cisco Unified CallManager 6.0.
Using your web browser, login to the Cisco Unified Communications Operating System Administration web page
Under the Software Upgrades menu, select Install/Upgrade.
Fill in the appropriate values in the Software Location section for the file you downloaded above, and click Next.
In the Available Software drop-down box, select the file you downloaded above, and click Next.
After validating the MD5 has the correct value, click Next.
In the Warning box, verify you have selected the correct firmware, then click Install.
Check that you received a Success message.
Note: In order to change the loads manually, you do NOT need to reinstall this Device Package. The new files will be present in the TFTP folder. Go to CCMAdmin->Device->Device Settings->Device Defaults and manually change the name of the load file (for specific device(s)) to the new load and click UPDATE.
Note: If you are rebooting the cluster, the next step does not need to be done.
The Cisco TFTP service now must be stopped and restarted on the TFTP server, then reset the affected devices for them to upgrade to the new load.
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...