Cisco 7925G Administration Guide - Page 74

Shared Key, LEAP or EAP-FAST, Auto AKM, Description, Related Topics

Page 74 highlights

Understanding the Phone Startup Process Chapter 3 Setting Up the Cisco Unified Wireless IP Phone 7925G Table 3-5 Cisco Unified Wireless IP Phone Startup Process (continued) Step Description Related Topics 3. Authenticating with access The Cisco Unified Wireless IP Phone 7925G begins the Authentication Methods, point authenticating process. page 2-16 • 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. 4. Configuring IP network If the wireless 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 wireless 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 Load ID The wireless IP phone checks to verify that the proper firmware is installed or if new firmware is available to download. • Phone Configuration Files and Profile Files, page 2-14 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. 6. Downloading config 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-14 • Resolving Startup and Connectivity Problems, page 10-1 3-18 Cisco Unified Wireless IP Phone 7925G Administration Guide for Cisco Unified Communications Manager 7.0(1) OL-15984-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244

3-18
Cisco Unified Wireless IP Phone 7925G Administration Guide for Cisco Unified Communications Manager 7.0(1)
OL-15984-01
Chapter 3
Setting Up the Cisco Unified Wireless IP Phone 7925G
Understanding the Phone Startup Process
3.
Authenticating with access
point
The Cisco Unified Wireless IP Phone 7925G 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,
page 2-16
4.
Configuring IP network
If the wireless 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 wireless 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 Load ID
The wireless 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-14
6.
Downloading config 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-14
Resolving Startup and
Connectivity Problems,
page 10-1
Table 3-5
Cisco Unified Wireless IP Phone Startup Process (continued)
Step
Description
Related Topics