Cisco 7912G Administration Guide - Page 134

Verifying Voice VLAN Configuration, Verifying that the Phones Have Not Been Intentionally Reset - factory reset

Page 134 highlights

Resolving Startup Problems Chapter 6 Troubleshooting the Cisco IP Phone Verifying Voice VLAN Configuration If the Cisco IP Phone appears to reset during heavy network usage (for example, following extensive web surfing on a computer connected to same switch as phone), it is likely that you do not have a voice VLAN configured. Isolating the phones on a separate, auxiliary VLAN increases the quality of the voice traffic. See "Understanding How the Cisco IP Phone Interacts with the Cisco Catalyst Family of Switches" section on page 2-3 for more details. Verifying that the Phones Have Not Been Intentionally Reset If you are not the only administrator with access to Cisco CallManager, you should verify that no one else has intentionally reset the phones. Eliminating DNS or Other Connectivity Errors If the phone continues to reset, follow this procedure. Procedure Step 1 Step 2 Step 3 Reset the phone to factory defaults. See the "Resetting the Cisco IP Phone" section on page 6-8 for details. Modify DHCP and IP settings. a. Disable DHCP. See the "Modifying DHCP Settings" section on page 4-9 for details. b. Assign static IP values to the phone. See the "Configuring IP Settings" section on page 4-15 for details. Use the same default router setting used for other functioning Cisco IP Phones. c. Assign TFTP server. See the "Configuring TFTP Options" section on page 4-28 for details. Use the same TFTP server used for other functioning Cisco IP Phones. On the Cisco CallManager server, verify that the local host files have the correct Cisco CallManager server name mapped to the correct IP address. Refer to Configuring The IP Hosts File on a Windows 2000 CallManager Server on Cisco.com: http://www.cisco.com/warp/customer/788/AVVID/cm_hosts_file.html 6-20 Cisco IP Phone Administration Guide for Cisco CallManager 3.3, Cisco IP Phones 7902G/7905G/7912G 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 6
Troubleshooting the Cisco IP Phone
Resolving Startup Problems
6-20
Cisco IP Phone Administration Guide for Cisco CallManager 3.3, Cisco IP Phones 7902G/7905G/7912G
OL-6313-01
Verifying Voice VLAN Configuration
If the Cisco IP Phone appears to reset during heavy network usage (for example,
following extensive web surfing on a computer connected to same switch as
phone), it is likely that you do not have a voice VLAN configured.
Isolating the phones on a separate, auxiliary VLAN increases the quality of the
voice traffic. See
“Understanding How the Cisco IP Phone Interacts with the
Cisco Catalyst Family of Switches” section on page 2-3
for more details.
Verifying that the Phones Have Not Been Intentionally Reset
If you are not the only administrator with access to Cisco CallManager, you
should verify that no one else has intentionally reset the phones.
Eliminating DNS or Other Connectivity Errors
If the phone continues to reset, follow this procedure.
Procedure
Step 1
Reset the phone to factory defaults. See the
“Resetting the Cisco IP Phone”
section on page 6-8
for details.
Step 2
Modify DHCP and IP settings.
a.
Disable DHCP. See the
“Modifying DHCP Settings” section on page 4-9
for
details.
b.
Assign static IP values to the phone. See the
“Configuring IP Settings”
section on page 4-15
for details. Use the same default router setting used for
other functioning Cisco IP Phones.
c.
Assign TFTP server. See the
“Configuring TFTP Options” section on
page 4-28
for details. Use the same TFTP server used for other functioning
Cisco IP Phones.
Step 3
On the Cisco CallManager server, verify that the local host files have the correct
Cisco CallManager server name mapped to the correct IP address. Refer to
Configuring The IP Hosts File on a Windows 2000 CallManager Server
on
Cisco.com: