Cisco 8831NR Administration Manual page 48

Phone Startup Process
Communications Manager that requires the conference phone to be reset, a change is made to the conference
phone configuration file automatically.
Configuration files also contain information about which image load the conference phone should be running.
If this image load differs from the one currently loaded, the phone contacts the TFTP server to request the
required load files.
A conference phone accesses a default configuration file named XmlDefault.cnf.xml from the TFTP
server when these conditions exist:
• You have enabled autoregistration in Cisco Unified Communications Manager
• The conference phone has not been added to the Cisco Unified Communications Manager Database
• The conference phone is registering for the first time
If autoregistration 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 conference phone will
reset and attempt to register repeatedly.
If the conference phone has registered before, the conference phone will access the configuration file named
SEPmac_address.cnf.xml, where the mac_address portion of the filename is the Media Access
Control (MAC) address of the conference phone.
Phone Startup Process
When connecting to the VoIP network, the conference phone goes through a standard startup process, as
described in the following table. Depending on your specific network configuration, not all of these process
steps may occur on your conference phone.
1. Obtain power from the switch. If a conference phone is not using external power, the switch provides
in-line power through the Ethernet cable attached to the conference phone. For more information, see
Conference Phone Power, on page
2. Load the stored conference phone image. The conference phone has non-volatile flash memory in which
it stores firmware images and user-defined preferences. At startup, the conference phone runs a bootstrap
loader that loads a conference phone image stored in flash memory. Using this image, the conference
phone initializes its software and hardware. For more information, see .
3. Configure VLAN. If the Cisco Unified IP Conference Phone is connected to a Cisco switch, the switch
next informs the phone of the voice VLAN defined on the switch port. The phone needs to know its VLAN
membership before it can proceed with the Dynamic Host Configuration Protocol (DHCP) request for an
IP address.
4. Obtain an IP address . If the Cisco Unified IP Conference Phone uses DHCP to obtain an IP address, the
phone queries the DHCP server to obtain one. If you do not use DHCP in your network, you must assign
static IP addresses to each phone locally.
5. Access a TFTP server. In addition to assigning an IP address, the DHCP server directs the Cisco Unified
IP Conference Phone to a TFTP server. If the phone has a statically defined IP address, you must configure
the TFTP server locally on the phone. The phone then contacts the TFTP server directly.
Cisco Unified IP Conference Phone 8831 and 8831NR Administration Guide
38
Cisco Unified IP Phones and Telephony Networks
35.