Cisco 7971G-GE Administration Guide - Page 45

Understanding the Phone Startup Process - sip firmware

Page 45 highlights

Chapter 2 Preparing to Install the Cisco Unified IP Phone on Your Network Understanding the Phone Startup Process 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 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 resets and attempts to register repeatedly. If the phone has registered before, the phone accesses the configuration file named SEPmac_address.cnf.xml, where mac_address is the MAC address of the phone. For SIP phones, the TFTP server generates these SIP configuration files: • SIP IP Phone: - For unsigned and unencrypted files-SEP.cnf.xml - For signed files-SEP.cnf.xml.sgn - For signed and encrypted files-SEP.cnf.xml.enc.sgn • Dial Plan-.xml • Softkey Template-.xml The filenames are derived from the MAC Address and Description fields in the Phone Configuration window of Cisco Unified Communications Manager Administration. The MAC address uniquely identifies the phone. For more information refer to Cisco Unified Communications Manager Administration Guide. For more information about how the phone interacts with the TFTP server, refer to Cisco Unified Communications Manager System Guide, "Cisco TFTP" chapter. Understanding the Phone Startup Process When connecting to the VoIP network, the Cisco Unified IP Phone goes through a standard startup process, as described in Table 2-4. Depending on your specific network configuration, not all of these process steps may occur on your Cisco Unified IP Phone. Table 2-4 Cisco Unified IP Phone Startup Process Task Purpose Related Topics 1. Obtaining Power from the Switch. See the "Providing Power to the Phone" section on If a phone is not using external power, the switch provides page 2-3. in-line power through the Ethernet cable that is attached to See the "Resolving Startup Problems" section on the phone. page 9-1. 2. Loading the StoredPhone Image. See the "Resolving Startup Problems" section on The Cisco Unified IP Phone has non-volatile flash memory page 9-1. in which it stores firmware images and user-defined preferences. At startup, the phone runs a bootstrap loader that loads a phone image stored in flash memory. Using this image, the phone initializes its software and hardware. OL-15299-01 Cisco Unified IP Phone 7970G/7971G-GE Administration Guide for Cisco Unified Communications Manager 7.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

2-7
Cisco Unified IP Phone 7970G/7971G-GE Administration Guide for Cisco Unified Communications Manager 7.0
OL-15299-01
Chapter 2
Preparing to Install the Cisco Unified IP Phone on Your Network
Understanding the Phone Startup Process
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
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 resets and attempts to register repeatedly.
If the phone has registered before, the phone accesses the configuration file named
SEP
mac_address
.cnf.xml, where
mac_address
is the MAC address of the phone.
For SIP phones, the TFTP server generates these SIP configuration files:
SIP IP Phone:
For unsigned and unencrypted files—SEP
<mac>
.cnf.xml
For signed files—SEP
<mac>
.cnf.xml.sgn
For signed and encrypted files—SEP
<mac>
.cnf.xml.enc.sgn
Dial Plan—
<dialplan>
.xml
Softkey Template—
<softkey_template>
.xml
The filenames are derived from the MAC Address and Description fields in the Phone Configuration
window of Cisco Unified Communications Manager Administration. The MAC address uniquely
identifies the phone. For more information refer to
Cisco Unified Communications Manager
Administration Guide
.
For more information about how the phone interacts with the TFTP server, refer to
Cisco Unified
Communications Manager System Guide
, “Cisco TFTP” chapter.
Understanding the Phone Startup Process
When connecting to the VoIP network, the Cisco Unified IP Phone goes through a standard startup
process, as described in
Table 2-4
. Depending on your specific network configuration, not all of these
process steps may occur on your Cisco Unified IP Phone.
Table 2-4
Cisco Unified IP Phone Startup Process
Task
Purpose
Related Topics
1.
Obtaining Power from the Switch.
If a phone is not using external power, the switch provides
in-line power through the Ethernet cable that is attached to
the phone.
See the
“Providing Power to the Phone” section on
page 2-3
.
See the
“Resolving Startup Problems” section on
page 9-1
.
2.
Loading the StoredPhone Image.
The Cisco Unified IP Phone has non-volatile flash memory
in which it stores firmware images and user-defined
preferences. At startup, the phone runs a bootstrap loader
that loads a phone image stored in flash memory. Using this
image, the phone initializes its software and hardware.
See the
“Resolving Startup Problems” section on
page 9-1
.