Phone Startup Process - Cisco 8831 Administration Manual

Phone startup process

• You have enabled auto-registration 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 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 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
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. For more information, see
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. For more information, see the
problems.
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.
You can also assign an alternative TFTP server to use instead of the one that DHCP assigns.
Note
For more information, see
6 Request the configuration file. The TFTP server has configuration files, which define parameters for
connecting to Cisco Unified Communications Manager and other information for the conference phone.
For more information, see
7 Contact Cisco Unified Communications Manager. The configuration file defines how the conference phone
communicates with Cisco Unified Communications Manager and provides a conference phone with its
Cisco Unified IP Conference Phone 8831 Administration Guide for Cisco Unified Communications Manager
9.0
40
and Startup problems.
Network Setup menu
Network Setup menu and Startup
Phone configuration files and
Cisco Unified IP Phones and telephony networks
Startup problems.
and Startup problems.
Network Setup menu
problems.
Startup problems.
and Startup