I am trying to add the firmware for a 7921 wireless phone to CM 4.1 I downloaded and installed the firmware on the pub, and copied it to the tftp server. However, going into device defauts, does not show the new phone. Any thoughts?
CCM 4.1(3) does support the 7921G depending on what SR's are installed. The configuration of CCM will determine what steps are necessary to add support for the 7921G as a selectable phone model/type;
When deploying Cisco Unified Wireless IP Phone 7921G for the first time, you must install the 7921G Device Pack to add the new phone type to Cisco Unified CallManager.
To make the Cisco Unified Wireless IP Phone 7921G available in the Cisco Unified CallManager system, you might need to upgrade your system with the latest DevPack patch for your release of Cisco Unified CallManager. Check the ReadMe file (cmterm-7921-sccp.1-0-1-Readme.htm) that is posted with the firmware version 1.0(1) for more information.
You need to install the Device Package (see readme) to add support for the 7921 in CCM. Here is a clip of the install notes;
Perform the following procedure to install Cisco Unified CallManager Device Package X.X.exe:
1. Download the ciscocm-4-1-DevPack-X.X.exe file to your hard drive. Make a note of the location where you saved the file.
2. Double-click on the downloaded file to begin the installation.
3. Click Yes when the installation process displays a message that asks if you want to install this Device Package.
4. The remainder of the installation process continues without any additional user input.
5. Towards the end of the install it will prompt you "Update ALL devices firmware defaults?", (IMPORTANT) If you click "yes", it will change the default firmware load for all devices to the latest load packaged with this device pack, click "no" if you want to change the loads manually yourself later.
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 C:\Program Files\Cisco\TFTPPath folder. Go to CCMAdmin->System->Device Defaults and manually change the name of the load file (for specific device(s)) to the new load and click UPDATE. Next, reset the affected devices for them to upgrade to the new load.
The system will ask you if you want to view the logfile when the installation is complete.
6. Verify that the installation completed successfully by taking the following actions:
a. When the system prompts you to view the log file, if the number of errors listed in the dialog is "0", you can select No.
b. If the number of errors detected was greater than 0, select Yes to view the logfile and scroll down to the end of the log file. The errors section at the bottom of the log file will be updated with a corresponding severity.
c. Reset affected devices in order for them to obtain new firmware loads, or reboot the cluster.
Note: If the TFTP server is a separate server from the Publisher, the Cisco TFTP service needs to be stopped and restarted on the TFTP server before performing this step, unless the cluster (including the TFTP server) is being rebooted.
With the install of the devpak Step # 5 is very important. You probably don't want to change all of your existing phones firmware so be careful to answer NO if you don't want all models (7940/7960/7941/7961 etc) to have their default load updated.
Thanks for the input. I have heard alot of bad things about applying device packs, and that is it better to deploy SR's. Any comments? I am on 4.13SReB. I was thinking about going to SR5 or SR6 The SR upgrade says to update the OS also. I am at 2000.4.4ASR4. Is this advisable, and, if so, in which order to I upgrade? thanks for any help
I totally agree! In most cases (like yours) I much prefer the upgrade of SR's rather than just the new Devpak. For 4.1.3 SR 6 is very new as it was only released on December 3rd. I have not read alot of great things about SR 5, so I would go with something other than it.
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...