Cisco 7925G Administration Guide - Page 44

Interacting with Cisco Unified Communications Manager, Phone Configuration Files and Profile Files

Page 44 highlights

Components of the VoIP Wireless Network Chapter 2 Overview of the VoIP Wireless Network Implementing QoS in the connected Ethernet switch is highly desirable to maintain good voice quality. The COS and DSCP values that the Cisco Unified Wireless IP Phone 7925G sets do not need to be modified. To configure QoS correctly on the AP, see the "Wireless Network Requirements for VoIP" section on page 2-21. Related Topics • Authentication Methods, page 2-16 • Interacting with Cisco Unified Communications Manager, page 2-14 • VoIP WLAN Configuration, page 2-21 Interacting with Cisco Unified Communications Manager Cisco Unified Communications Manager is the call control component in the network that handles and routes calls for the wireless IP phones. Cisco Unified Communications Manager manages the components of the IP telephony system-the phones, access gateways, and the resources-for such features as call conferencing and route planning. When deploying Cisco Unified Wireless IP Phone 7925G, you must use Cisco Unified Communications Manager Release 4.1, 4.2, 4.3, 5.1, 6.0(1), 6.1(1) or 7.0(1) and SCCP protocol. Before Cisco Unified Communications Manager can recognize a phone, it must register with Cisco Unified Communications Manager and be configured in the database. For information about setting up phones in Cisco Unified Communications Manager, see the "Overview of Configuring and Installing the Cisco Unified Wireless IP Phone 7925G" section on page 1-14. You can find more information about configuring Cisco Unified Communications Manager to work with the IP phones and IP devices in the Cisco Unified Communications Manager Administration Guide and Cisco Unified Communications Manager System Guide. Related Topics • Overview of Configuring and Installing the Cisco Unified Wireless IP Phone 7925G, page 1-14 • Phone Configuration Files and Profile Files, page 2-14 Phone Configuration Files and Profile Files Configuration files for a phone define parameters for connecting to Cisco Unified Communications Manager and are stored on the TFTP server. In general, any time you make a change in Cisco Unified Communications Manager Administration that requires resetting the phone, the phone configuration file changes automatically. Configuration files also contain information about the correct image load for the phone. If this image load differs from the one currently loaded on a phone, the phone contacts the TFTP server to request the new image file. The phone first requests the configuration file SEPxxxxxxxxxxxx.cnf.xml, where each xx is the two-digit lowercase hexadecimal representation of each integer in the MAC address. If the phone cannot find this file, it requests the configuration file XMLDefault.cnf.xml. After the phone obtains the *.cnf.xml files, it requests a phone-specific profile file. If a phone cannot find this profile file, it requests the appropriate common profile file. After the phone finds one of the profile files, or if it cannot find a profile file, it continues with its startup process. 2-14 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

2-14
Cisco Unified Wireless IP Phone 7925G Administration Guide for Cisco Unified Communications Manager 7.0(1)
OL-15984-01
Chapter 2
Overview of the VoIP Wireless Network
Components of the VoIP Wireless Network
Implementing QoS in the connected Ethernet switch is highly desirable to maintain good voice quality.
The COS and DSCP values that the Cisco Unified Wireless IP Phone 7925G sets do not need to be
modified. To configure QoS correctly on the AP, see the
“Wireless Network Requirements for VoIP”
section on page 2-21
.
Related Topics
Authentication Methods, page 2-16
Interacting with Cisco Unified Communications Manager, page 2-14
VoIP WLAN Configuration, page 2-21
Interacting with Cisco Unified Communications Manager
Cisco Unified Communications Manager is the call control component in the network that handles and
routes calls for the wireless IP phones. Cisco Unified Communications Manager manages the
components of the IP telephony system—the phones, access gateways, and the resources—for such
features as call conferencing and route planning. When deploying Cisco Unified Wireless
IP Phone 7925G, you must use Cisco Unified Communications Manager Release 4.1, 4.2, 4.3, 5.1,
6.0(1), 6.1(1) or 7.0(1) and SCCP protocol.
Before Cisco Unified Communications Manager can recognize a phone, it must register with Cisco
Unified Communications Manager and be configured in the database. For information about setting up
phones in Cisco Unified Communications Manager, see the
“Overview of Configuring and Installing the
Cisco Unified Wireless IP Phone 7925G” section on page 1-14
.
You can find more information about configuring Cisco Unified Communications Manager to work with
the IP phones and IP devices in the
Cisco Unified Communications Manager Administration Guide
and
Cisco Unified Communications Manager System Guide.
Related Topics
Overview of Configuring and Installing the Cisco Unified Wireless IP Phone 7925G, page 1-14
Phone Configuration Files and Profile Files, page 2-14
Phone Configuration Files and Profile Files
Configuration files for a phone define parameters for connecting to Cisco Unified Communications
Manager and are stored on the TFTP server. In general, any time you make a change in Cisco
Unified Communications Manager Administration that requires resetting the phone, the phone
configuration file changes automatically.
Configuration files also contain information about the correct image load for the phone. If this image
load differs from the one currently loaded on a phone, the phone contacts the TFTP server to request the
new image file.
The phone first requests the configuration file SEP
xxxxxxxxxxxx
.cnf.xml, where each
xx
is the two-digit
lowercase hexadecimal representation of each integer in the MAC address. If the phone cannot find this
file, it requests the configuration file XMLDefault.cnf.xml.
After the phone obtains the *.cnf.xml files, it requests a phone-specific profile file. If a phone cannot
find this profile file, it requests the appropriate common profile file.
After the phone finds one of the profile files, or if it cannot find a profile file, it continues with its startup
process.