Cisco 7912G Administration Guide - Page 46

Accessing TFTP Server, Requesting Configuration Files

Page 46 highlights

Understanding the Phone Startup Process Chapter 2 Preparing to Install the Cisco IP Phone on Your Network Related Topics • Understanding the Phone Startup Process, page 2-4 • Modifying DHCP Settings, page 4-9 • Configuring IP Settings, page 4-15 • Resolving Startup Problems, page 6-12 Accessing TFTP Server In addition to assigning an IP address, the DHCP server directs the Cisco IP Phone to a TFTP Server. If the phone has a statically defined IP address, you must configure the TFTP server locally on the phone; the phone then contacts the TFTP server directly. Related Topics • Understanding the Phone Startup Process, page 2-4 • Configuring TFTP Options, page 4-28 • Resolving Startup Problems, page 6-12 Requesting Configuration Files The TFTP server has configuration files (.cnf file format or .cnf.xml) for telephony devices, which define parameters for connecting to Cisco CallManager. In general, any time you make a change in Cisco CallManager that requires the phone (device) to be reset, a change has been made to the phone's configuration file. The .cnf.xml file also contains the information that tells the phone which image load it should be running. If this image load differs from the one currently loaded on the phone, the phone contacts the TFTP server to request the new image file. The phone first requests the file SEPxxxxxxxxxxxx.cnf.xml, where each xx is the two-digit lowercase hexadecimal representation of each integer in the phone's MAC address. If the phone cannot find this file, it requests the files XMLDefault.cnf.xml and SEDDefault.cnf. Cisco IP Phone Administration Guide for Cisco CallManager 3.3, Cisco IP Phones 7902G/7905G/7912G 2-6 OL-6313-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

Chapter 2
Preparing to Install the Cisco IP Phone on Your Network
Understanding the Phone Startup Process
2-6
Cisco IP Phone Administration Guide for Cisco CallManager 3.3, Cisco IP Phones 7902G/7905G/7912G
OL-6313-01
Related Topics
Understanding the Phone Startup Process, page 2-4
Modifying DHCP Settings, page 4-9
Configuring IP Settings, page 4-15
Resolving Startup Problems, page 6-12
Accessing TFTP Server
In addition to assigning an IP address, the DHCP server directs the
Cisco IP Phone to a TFTP Server. If the phone has a statically defined IP address,
you must configure the TFTP server locally on the phone; the phone then contacts
the TFTP server directly.
Related Topics
Understanding the Phone Startup Process, page 2-4
Configuring TFTP Options, page 4-28
Resolving Startup Problems, page 6-12
Requesting Configuration Files
The TFTP server has configuration files (.cnf file format or .cnf.xml) for
telephony devices, which define parameters for connecting to Cisco
CallManager.
In general, any time you make a change in Cisco CallManager that requires the
phone (device) to be reset, a change has been made to the phone's configuration
file.
The .cnf.xml file also contains the information that tells the phone which image
load it should be running. If this image load differs from the one currently loaded
on the phone, the phone contacts the TFTP server to request the new image file.
The phone first requests the file SEP
xxxxxxxxxxxx
.cnf.xml, where each
xx
is the
two-digit lowercase hexadecimal representation of each integer in the phone’s
MAC address. If the phone cannot find this file, it requests the files
XMLDefault.cnf.xml and SEDDefault.cnf.