Cisco 7921G Administration Guide - Page 203

Logging Information for Troubleshooting, Using a System Log Server

Page 203 highlights

Chapter 10 Troubleshooting the Cisco Unified Wireless IP Phone 7921G General Troubleshooting Information Table 10-3 Cisco Unified Wireless IP Phone Troubleshooting Tips (continued) Summary Explanation Call established with the iLBC protocol does Call statistics display does not show iLBC as the receiver/sender codec. not show that the iLBC codec is being used 1. Check the following using the Cisco Unified Communications Manager administration pages: - Both phones are in the iLBC device pool. - The iLBC device pool is configured with the iLBC region. - The iLBC region is configured with the iLBC codec. 2. Capture a sniffer trace between the phone and Cisco Unified Communications Manager and verify that SCCP messages, OpenReceiveChannel, and StationMediaTransmit messages have media payload type value equal to 86. If so, the problem is with the phone; otherwise the problem is with the Cisco Unified Communications Manager configuration. 3. Enable audio server debug and capture logs from both phones. If needed, enable Java debug. Related Topics • Logging Information for Troubleshooting, page 10-17 • General Troubleshooting Information, page 10-14 Logging Information for Troubleshooting The following options can help you gather troubleshooting information: • Using a System Log Server, page 10-17 • Using the Trace Logs on the Unified IP Phone, page 10-17 Using a System Log Server To gather information about problems with the wired network that can cause roaming delays or no connectivity, set up a system log server. Enable "syslog" on the network switches and access points that is logged to the system log server. Also enable Network Time Protocol (NTP) so that all access points and switches use the same times. For information about setting up a system log server, see "Configuring Trace Settings" section on page 4-29. Using the Trace Logs on the Unified IP Phone When you are experiencing problems with registering with Cisco Unified Communications Manager, or call connections, you can use this function to trace the path of a packet from the phone to Cisco Unified Communications Manager. The result shows the number of hops and the IP address of each hop to reach the Cisco Unified Communications Manager server. You can use this information to check connectivity between the phone, Cisco Unified Communications Manager servers and gateways during a call. OL-15985-01 Cisco Unified Wireless IP Phone 7921G Administration Guide for Cisco Unified Communications Manager Release 7.0 10-17

  • 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

10-17
Cisco Unified Wireless IP Phone 7921G Administration Guide for Cisco Unified Communications Manager Release 7.0
OL-15985-01
Chapter 10
Troubleshooting the Cisco Unified Wireless IP Phone 7921G
General Troubleshooting Information
Related Topics
Logging Information for Troubleshooting, page 10-17
General Troubleshooting Information, page 10-14
Logging Information for Troubleshooting
The following options can help you gather troubleshooting information:
Using a System Log Server, page 10-17
Using the Trace Logs on the Unified IP Phone, page 10-17
Using a System Log Server
To gather information about problems with the wired network that can cause roaming delays or no
connectivity, set up a system log server. Enable “syslog” on the network switches and access points that
is logged to the system log server. Also enable Network Time Protocol (NTP) so that all access points
and switches use the same times.
For information about setting up a system log server, see
“Configuring Trace Settings” section on
page 4-29
.
Using the Trace Logs on the Unified IP Phone
When you are experiencing problems with registering with Cisco Unified Communications Manager, or
call connections, you can use this function to trace the path of a packet from the phone to
Cisco Unified Communications Manager. The result shows the number of hops and the IP address of
each hop to reach the Cisco Unified Communications Manager server. You can use this information to
check connectivity between the phone, Cisco Unified Communications Manager servers and gateways
during a call.
Call established with the iLBC protocol does
not show that the iLBC codec is being used
Call statistics display does not show iLBC as the receiver/sender codec.
1.
Check the following using the Cisco Unified Communications Manager
administration pages:
Both phones are in the iLBC device pool.
The iLBC device pool is configured with the iLBC region.
The iLBC region is configured with the iLBC codec.
2.
Capture a sniffer trace between the phone and Cisco Unified
Communications Manager and verify that SCCP messages,
OpenReceiveChannel, and StationMediaTransmit messages have media
payload type value equal to 86. If so, the problem is with the phone;
otherwise the problem is with the Cisco Unified Communications
Manager configuration.
3.
Enable audio server debug and capture logs from both phones. If needed,
enable Java debug.
Table 10-3
Cisco Unified Wireless IP Phone Troubleshooting Tips (continued)
Summary
Explanation