2-6
Cisco Unified IP Phone 6901 and 6911 Administration Guide for Cisco Unified Communications Manager 8.5 (SCCP and SIP)
OL-23874-01
Chapter 2 Preparing to Install the Cisco Unified IP Phone on Your Network
Understanding the Phone Startup Process
• 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.
If the phone is registered and working in encrypted mode, the phone accesses the configuration file
named SEPmac_address.cnf.xml.enc.sgn. If the SEPmac_address.cnf.xml.enc.sgn does not exist on the
TFTP server, the phone requests for the file SEPmac_address.cnf.xml.sgn. That is, if phone works in
encrypted mode with TFTP Encrypted Config selected, the phone accesses the configuration file named
SEPMac_addr.cnf.xml.enc.sgn if it is not chosen, SEPMac_addr.cnf.xml.sgn is chosen. To enable TFTP
Encrypted Configuration, select the TFTP Encrypted Config check box Phone Security Profile
Configuration page. You can access this page from the Cisco Unified CM Administration UI by selecting
System > Security> Phone Security Profile and then clicking Add New.
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
The filenames are derived from the MAC address and description fields in the Phone Configuration
window of Cisco Unified Communications Manager Administration. The MAC address uniquely
identifies the phone.
For more information on phone configuration settings, go to the Cisco Unified IP Phone Configuration
chapter in the Cisco Communications Manager Administration Guide.
Understanding the Phone Startup Process
When connecting to the VoIP network, the Cisco Unified IP Phone 6901 and 6911 go through a standard
startup process that is described in Table 2-3. Depending on your specific network configuration, not all
of these steps may occur on your Cisco Unified IP Phone.
Tab l e 2-3 Cisco Unified IP Phone Startup Process
Task Purpose Related Topics
1. Obtaining Power from the Switch
If a phone is not using external power, the switch provides in-line power
through the Ethernet cable attached to the phone.
• Adding Phones to the Cisco
Unified Communications
Manager Database, page 2-7.
• Resolving Startup Problems,
page 7-1.
2. Configuring VLAN
If the Cisco Unified IP Phone is connected to a Cisco Catalyst switch, the
switch next informs the phone of the voice VLAN defined on the switch.
The phone needs to know its VLAN membership before it can proceed with
the Dynamic Host Configuration Protocol (DHCP) request for an IP address.
• Configuring Settings on the
Cisco Unified IP Phone,
page 4-1.
• Resolving Startup Problems,
page 7-1.