Cisco IP Communicator Administration Manual page 35

Chapter 1 An Overview of Cisco IP Communicator
Additionally, it can use HTTP to retrieve software updates, thereby accelerating
file transfer for remote users. (See the
Administration Tool" section on page 2-14
If you do not use DHCP on your network to identify TFTP servers, or if you want
the device to use an alternate TFTP server, then you need to manually configure
your TFTP server from the Cisco IP Communicator interface—or instruct users to
do this task. (See the
Step Two—Requesting Configuration Files
Configuration files (.cnf.xml) reside on the TFTP server and define parameters for
connecting to Cisco CallManager. In general, any time you make a change in
Cisco CallManager that requires a device to be reset, a change has been made to
the device's configuration file.
•
•
Step Three—Updating Software
If you have opted to use AutoUpdate, the .cnf.xml file also contains the
information that tells Cisco IP Communicator which software version it should be
running. If this software version differs from the one currently in use,
Cisco IP Communicator contacts the TFTP server to request the new software
file. To make this request, Cisco IP Communicator first tries to use HTTP. If you
have not enabled HTTP access, Cisco IP Communicator will use TFTP.
Step Four—Contacting Cisco CallManager
After obtaining the configuration file from the TFTP server,
Cisco IP Communicator attempts to make a TCP connection to the highest
priority Cisco CallManager on the list.
OL-4698-01
"Specifying a TFTP Server" section on page
If you have enabled auto-registration in Cisco CallManager,
Cisco IP Communicator accesses a default configuration file
(xmldefault.cnf.xml) from the TFTP server.
Otherwise, Cisco IP Communicator accesses a .cnf.xml file corresponding to
its device name.
Cisco IP Communicator Administration Guide for Cisco CallManager
Understanding the Startup Process
"Running the Cisco IP Communicator
for instructions.)
4-8.)
1-11