![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/8/e5/8e5197c3-4971-4da0-a984-45c3d0ba361d/8e5197c3-4971-4da0-a984-45c3d0ba361d-bg9.png)
2-9
Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager 4.2, Cisco Unified IP Phones
OL-8555-01
Chapter 2 Preparing to Install the Cisco Unified IP Phone on Your Network
Understanding the Phone Startup Process
7. Requesting the
Configuration File.
The TFTP server has configuration files, which
define parameters for connecting to
Cisco Unified CallManager and other information
for the phone.
• “Understanding
Phone
Configuration
Files” section on
page 2-6
• Configuring
Security on the
Cisco Unified IP
Phone, page 3-16
• Resolving Startup
Problems,
page 8-2.
8. Contacting
Cisco Unified
CallManager.
The configuration file defines how the
Cisco Unified IP Phone communicates with
Cisco Unified CallManager. After obtaining the
file from the TFTP server, the phone attempts to
make a connection to the highest priority
Cisco Unified CallManager on the list. If security
is implemented, the phone makes a TLS
connection. Otherwise, it makes a non-secure TCP
connection.
If the phone was manually added to the database,
Cisco Unified CallManager identifies the phone.
If the phone was not manually added to the
database and auto-registration is enabled in
Cisco Unified CallManager, the phone attempts to
auto-register itself in the
Cisco Unified CallManager database.
Note Auto-registration must be disabled if
security is implemented.
Cisco Unified CallManager informs devices using
.cnf format configuration files of their load ID.
Devices using .xml format configuration files
receive the load ID in the configuration file.
Resolving Startup
Problems, page 8-2.
Table 2-1 Cisco Unified IP Phone Startup Process (continued)
Step Description Related Topics