Cisco CP-7911G Administration Guide - Page 61

Understanding Phone Configuration Files

Page 61 highlights

Chapter 2 Preparing to Install the Cisco Unified IP Phone on Your Network Understanding Phone Configuration Files Understanding Phone Configuration Files Configuration files for a phone are stored on the TFTP server and define parameters for connecting to Cisco Unified Communications Manager. In general, any time you make a change in Cisco Unified Communications Manager that requires the phone to be reset, a change is made to the phone's configuration file automatically. Configuration files also contain information about which image load the phone should be running. If this image load differs from the one currently loaded on a phone, the phone contacts the TFTP server to request the required load files. These files are digitally signed to ensure the authenticity of the files' source. In addition, if the device security mode in the configuration file is set to Authenticated and the CTL file on the phone has a valid certificate for Cisco Unified Communications Manager, the phone establishes a TLS connection to Cisco Unified Communications Manager. Otherwise, the phone establishes a TCP connection. Note If the device security mode in the configuration file is set to Authenticated or Encrypted but the phone has not received a CTL file, the phone will continuously try to obtain a CTL file so that it can register securely. If you configure security-related settings in Cisco Unified Communications Manager Administration, the phone configuration file will contain sensitive information. To ensure the privacy of a configuration file, you must configure it for encryption. For detailed information, refer to the "Configuring Encrypted Phone Configuration Files" chapter in Cisco Unified Communications Manager Security Guide. A phone requests a configuration file whenever it resets and registers with Cisco Unified Communications Manager. A phone accesses a default configuration file named XmlDefault.cnf.xml from the TFTP server when these conditions exist: • You have enabled auto-registration in Cisco Unified Communications Manager • The phone has not been added to the Cisco Unified Communications Manager Database • The phone is registering for the first time OL11954-01 Cisco Unified IP Phone 7906G and 7911G for Cisco Unified Communications Manager 6.0 2-7

  • 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
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284

2-7
Cisco Unified IP Phone 7906G and 7911G for Cisco Unified Communications Manager 6.0
OL11954-01
Chapter 2
Preparing to Install the Cisco Unified IP Phone on Your Network
Understanding Phone Configuration Files
Understanding Phone Configuration Files
Configuration files for a phone are stored on the TFTP server and define
parameters for connecting to Cisco Unified Communications Manager. In
general, any time you make a change in Cisco Unified Communications Manager
that requires the phone to be reset, a change is made to the phone’s configuration
file automatically.
Configuration files also contain information about which image load the phone
should be running. If this image load differs from the one currently loaded on a
phone, the phone contacts the TFTP server to request the required load files.
These files are digitally signed to ensure the authenticity of the files’ source.
In addition, if the device security mode in the configuration file is set to
Authenticated and the CTL file on the phone has a valid certificate for
Cisco
Unified
Communications Manager, the phone establishes a TLS connection
to Cisco Unified Communications Manager. Otherwise, the phone establishes a
TCP connection.
Note
If the device security mode in the configuration file is set to Authenticated or
Encrypted but the phone has not received a CTL file, the phone will continuously
try to obtain a CTL file so that it can register securely.
If you configure security-related settings in Cisco Unified Communications
Manager Administration, the phone configuration file will contain sensitive
information. To ensure the privacy of a configuration file, you must configure it
for encryption. For detailed information, refer to the “Configuring Encrypted
Phone Configuration Files” chapter in
Cisco Unified Communications Manager
Security Guide
.
A phone requests a configuration file whenever it resets and registers with
Cisco Unified Communications Manager.
A phone accesses a default configuration file named XmlDefault.cnf.xml from the
TFTP server when these conditions exist:
You have enabled auto-registration in Cisco Unified Communications
Manager
The phone has not been added to the Cisco Unified Communications
Manager Database
The phone is registering for the first time