After a Cisco CallManager upgrade, some IP phones do not download the
new IP phone load from TFTP and do not register with the Cisco CallManager.
This document discusses and provides a resolution for this issue.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
Technical Tips Conventions for more information on document
After a Cisco CallManager upgrade, some of the IP phones do not boot up
completely. They are stuck in various states of the boot process that include
"Configuring CM List" and "Upgrading Software". The IP phones also do not
register with the Cisco CallManager and display the .cnf.xml
files cannot be located error message.
Complete these steps to resolve this problem:
Open the Cisco CallManager Administration page.
Select Service > Service
Select the CallManager server and choose Cisco
Tftp for the service.
Set these parameters under Clusterwide Parameters (parameters that
apply to all servers):
Set the value for Build CNF Files* to Build All.
Note: When you set the Build CNF Files service parameter to
Build All, the TFTP server builds both .cnf.xml and .cnf
format configuration files for all devices. When you set this service parameter
to Build None, the TFTP server builds only .cnf.xml files for
all devices. When this parameter is set to Build Selective,
which is the default value, the TFTP server builds .cnf.xml files for all
devices. It also builds .cnf files only for a select list of devices that do
not support .cnf.xml.
Set the Enable Caching of Constant and Bin Files at Startup
parameter to False.
Set the Enable Caching of Configuration Files parameter to
Note: By default, Enable Caching of Configuration Files is set to
True. When this parameter is set to True, all
the CNF and XML files are built and kept only in memory. When this parameter is
set to False, TFTP writes all the CNF and XML files to the
disk under the TFTP path C:\Program Files\Cisco\TFTPPath. It
can take a long time to write these files to the disk if a large number of
devices exist in the network. Therefore, set the Enable Caching of
Configuration Files parameter to False to reduce the
performance of the TFTP server.
Restart the Cisco TFTP service. Complete these steps:
Select Application > Cisco
CallManager Serviceability > Tools >
Click on the Cisco CallManager server, choose Cisco
TFTP and click Restart.
Note: You are now able to see the configuration files for the devices
in C:\Program Files\Cisco\TFTPPath.
Restart the affected Cisco IP phones.
Set the values of the Enable Caching of Constant and Bin Files at
Startup parameter and the Enable Caching of Configuration Files parameter back
Note: There are several problems that can cause a Cisco IP phone not to
register. Refer to
Cisco IP Phone (7910, 7940, 7960, 12 SP, and 30 VIP) Registration Problems with
Cisco CallManager 3.x and 4.0 for more information on those