Operation Manual

2-6
Cisco Unified IP Phone 7975G Administration Guide for Cisco Unified Communications Manager 6.1
OL-14640-01
Chapter 2 Preparing to Install the Cisco Unified IP Phone on Your Network
Understanding Phone Configuration Files
In addition, if the device security mode in the configuration file is set to Authenticated and the CTL file
on the phone has a valid certificate for Cisco
Unified Communications Manager, the phone establishes
a TLS connection to Cisco
Unified Communications Manager. Otherwise, the phone establishes a TCP
connection. For SIP phones, a TLS connection requires that the transport protocol in the phone
configuration file be set to TLS, which corresponds to the transport type in the SIP Security Profile in
Cisco Unified Communications Manager Administration.
Note If the device security mode in the configuration file is set to Authenticated or Encrypted, but the phone
has not received a CTL file, the phone continuously tries to obtain a CTL file, so it can register securely.
If you configure security-related settings in Cisco Unified Communications Manager Administration,
the phone configuration file will contain sensitive information. To ensure the privacy of a configuration
file, you must configure it for encryption. For detailed information, refer to the “Configuring Encrypted
Phone Configuration Files” chapter in Cisco Unified Communications Manager Security Guide.
A phone accesses a default configuration file named XmlDefault.cnf.xml from the TFTP server when
these conditions exist:
• You have enabled auto-registration in Cisco Unified Communications Manager
• The phone has not been added to the Cisco Unified Communications Manager Database
• The phone is registering for the first time
If auto registration is not enabled and the phone has not been added to the Cisco
Unified
Communications Manager database, the phone registration request will be rejected. In this case,
the phone resets and attempts to register repeatedly.
If the phone has registered before, the phone accesses the configuration file named
SEPmac_address.cnf.xml, where mac_address is the MAC address of the phone.
For SIP phones, the TFTP server generates these SIP configuration files:
• SIP IP Phone:
– For unsigned and unencrypted files—SEP<mac>.cnf.xml
– For signed files—SEP<mac>.cnf.xml.sgn
– For signed and encrypted files—SEP<mac>.cnf.xml.enc.sgn
• Dial Plan—<dialplan>.xml
• Softkey Template—<softkey_template>.xml
The filenames are derived from the MAC Address and Description fields in the Phone Configuration
window of Cisco
Unified Communications Manager Administration and the devicename field in the
Cisco
Unified Communications Manager database. The MAC address uniquely identifies the phone. For
more information refer to Cisco Unified Communications Manager Administration Guide.
For more information about how the phone interacts with the TFTP server, refer to Cisco Unified
Communications Manager System Guide, “Cisco TFTP” chapter.