Specifications

2-6
Cisco Unified IP Phone 7906G and 7911G for Cisco Unified Communications Manager 8.0
OL-21033-01
Chapter 2 Preparing to Install the Cisco Unified IP Phone on Your Network
Understanding the Phone Startup Process
Table 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.
See Providing Power to the
Cisco Unified IP Phone
7906G and 7911G, page 2-3.
See Resolving Startup Problems, page 9-1.
2. The Cisco IP Phone has non-volatile Flash memory in which it stores
firmware images and user-defined preferences. At startup, the phone
runs a bootstrap loader that loads a phone image stored in Flash
memory. Using this image, the phone initializes its software and
hardware.
See Resolving Startup Problems, page 9-1.
3. Configuring VLAN.
If the Cisco IP 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.
If a third-party switch is used and VLANs are configured, the VLAN on
the phone must be manually configured.
See Network Configuration Menu,
page 4-5.
See Resolving Startup Problems, page 9-1.
4. Obtaining an IP Address.
If the Cisco IP Phone is using DHCP to obtain an IP address, the phone
queries the DHCP server to obtain one. If you are not using DHCP in
your network, you must assign static IP addresses to each phone locally.
In addition to assigning an IP address, the DHCP server directs the
Cisco Unified IP 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.
Note You can also assign an alternative TFTP server to use instead of
the one assigned by DHCP.
See Network Configuration Menu,
page 4-5.
See Resolving Startup Problems, page 9-1.
5. Accessing a TFTP Server. See Network Configuration Menu,
page 4-5.
See Resolving Startup Problems, page 9-1.
6. Requesting the CTL file.
The TFTP server stores the CTL file. This file contains the certificates
necessary for establishing a secure connection between the phone and
Cisco Unified Communications Manager.
Refer to the
Cisco Unified Communications Manager
Security Guide, Configuring the Cisco
CTL Client.
7. Requesting the ITL file
The phone requests the ITL file after it requests the CTL file. The ITL
file contains the certificates of the entities that the phone can trust. The
certificates are used for authenticating a secure connection with the
servers or to authenticating a digital signature signed by the servers.
Refer to the
Cisco Unified Communications Manager
Security Guide, Security by Default.