3-19
Cisco Unified Wireless IP Phone 7921G Administration Guide for Cisco Unified Communications Manager Release 7.0
OL-15985-01
Chapter 3 Setting Up the Cisco Unified Wireless IP Phone 7921G
Understanding the Phone Startup Process
3. Authenticating with access
point
The Cisco Unified Wireless IP Phone 7921G begins the
authenticating process.
•
If set for Open, then any device can authenticate to the
access point. For added security, static WEP
encryption might optionally be used.
•
If set to Shared Key, the phone encrypts the challenge
text using the WEP key and the access point must
verify that the WEP key was used to encrypt the
challenge text before network access is available.
•
If set for LEAP or EAP-FAST, then the user name
and password are authenticated by the RADIUS server
before network access is available.
•
If set for Auto (AKM), the phone looks for an access
point with one of the following key management
options enabled:
–
WPA, WPA2, or CCKM—The username and
password are authenticated by the RADIUS server
before network access is available.
–
WPA-Pre-shared key, WPA2-Pre-shared
key—The phone authenticates with the access
point using the pre-shared key.
“Authentication Methods”
section on page 2-14
4. Configuring an IP address
If the unified 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 a static IP address to each phone locally.
In addition to assigning an IP address, the DHCP server
directs the unified IP phone to a TFTP server. If the phone
has a statically defined IP address, you must configure the
TFTP server IP address locally on the phone; the phone
then contacts the TFTP server directly.
•
Configuring DHCP
Settings, page 5-6
•
Disabling DHCP, page 5-6
•
Resolving Startup and
Connectivity Problems,
page 10-1
5. Downloading the load ID
The unified IP phone checks to verify that the proper
firmware is installed or if new firmware is available to
download.
Cisco Unified Communications Manager informs devices
using “.cnf” or “cnf.xml” format configuration files of
their load ID. Devices using “.xml” format configuration
files receive the load ID in the configuration file.
•
Phone Configuration Files
and Profile Files, page 2-12
6. Downloading the
configuration file
The TFTP server has configuration files and profile files.
A configuration file includes parameters for connecting to
Cisco Unified Communications Manager and information
about which image load a phone should be running. A
profile file contains various parameters and values for
phone and network settings.
•
Configuring an Alternate
TFTP Server, page 5-7
•
Phone Configuration Files
and Profile Files, page 2-12
•
Resolving Startup and
Connectivity Problems,
page 10-1
Table 3-6
Cisco Unified Wireless IP Phone Startup Process (continued)
Step
Description
Related Topics
