Cisco 7940 Administration Guide - Page 35

Understanding Phone Configuration Files - registration rejected

Page 35 highlights

Chapter 2 Preparing to Install the Cisco Unified IP Phone on Your Network Understanding Phone Configuration Files Table 2-2 Related Documentation for Power Document Topics PoE Solutions Cisco Catalyst Switches Integrated Service Routers Cisco IOS Software URL http://www.cisco.com/en/US/netsol/ ns340/ns394/ns147/ns412/networking_solutions_package.html http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_su pport_series_home.html http://www.cisco.com/en/US/products/hw/routers/index.html http://www.cisco.com/en/US/products/sw/iosswrel/products_ios_cisco_ios _software_category_ home.html 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. A phone accesses a default configuration file named XmlDefault.cnf.xml from the TFTP server when the following 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 If auto registration is not enabled and the phone has not been added to the Cisco Unified Communications Manager Database, the phone registration request will be rejected. In this case, the phone will reset and attempt to register repeatedly. If the phone has registered before, the phone will access the configuration file named SEPmac_address.cnf.xml, where mac_address is the MAC address of the phone. OL-15498-01 Cisco Unified IP Phone 7960G/7940G Administration Guide for Cisco Unified Communications Manager 7.0 (SCCP) 2-5

  • 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

2-5
Cisco Unified IP Phone 7960G/7940G Administration Guide for Cisco Unified Communications Manager 7.0 (SCCP)
OL-15498-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.
A phone accesses a default configuration file named XmlDefault.cnf.xml from the TFTP server when
the following 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
If auto registration is not enabled and the phone has not been added to the
Cisco Unified Communications Manager Database, the phone registration request will be rejected. In
this case, the phone will reset and attempt to register repeatedly.
If the phone has registered before, the phone will access the configuration file named
SEPmac_address.cnf.xml, where mac_address is the MAC address of the phone.