3Com 3C10200 NBX Installation Guide - Page 195

Troubleshooting Actions continued

Page 195 highlights

System-level Troubleshooting 195 Table 36 Troubleshooting Actions (continued) Symptom Possible Cause Suggested Action Lose date and time when rebooting the system. Problem with the See "Servicing the Network Call Processor battery on the NCP. Battery" on page 197. NBX NetSet is very slow in responding. Your network uses a proxy server for Internet access. A common networking practice is to employ a proxy server to shield your network from intrusion by unauthorized users. However, communications with NBX NetSet do not need to pass through the proxy server. To speed access to NBX NetSet, configure your browser to access the NBX system without going through the proxy server. All greetings and prompts are missing. For example, calling the Auto Attendant or a user's mailbox produces silence instead of the expected greetings. The wrong message compression format was selected. Prior to R1.1.0, all audio used MuLaw compression. With R1.1.0, audio, that is, any prompt, message, or greeting, was recorded using ADPCM compression. If you are running R1.1.0 or higher, you must leave the compression format set to ADPCM. The ability to select the format allows you to migrate existing data into an older database for backwards compatibility. In release R2.6 and all later releases, the compression is set to ADPCM and you cannot change it. Caller ID information is not appearing when an outside call arrives. Your local telephone company is not providing Caller ID service to you. Caller ID is typically an optional service which you must order from your telephone company. You may be able to see caller ID by number or by name (or both) depending on the service your telephone company provides. You are answering the telephone before the Caller ID information is fully received. Caller ID information does not appear immediately. It usually appears between the first and second rings. If you answer the call too quickly, the information is never received.

  • 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
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248

System-level Troubleshooting
195
Lose date and
time when
rebooting the
system.
Problem with the
battery on the NCP.
See
Servicing the Network Call Processor
Battery
on
page 197
.
NBX NetSet is
very slow in
responding.
Your network uses a
proxy server for
Internet access.
A common networking practice is to
employ a proxy server to shield your
network from intrusion by unauthorized
users. However, communications with
NBX NetSet do not need to pass through
the proxy server. To speed access to NBX
NetSet, configure your browser to access
the NBX system without going through
the proxy server.
All greetings and
prompts are
missing. For
example, calling
the Auto
Attendant or a
user’s mailbox
produces silence
instead of the
expected
greetings.
The wrong message
compression format
was selected.
Prior to R1.1.0, all audio used MuLaw
compression. With R1.1.0, audio, that is,
any prompt, message, or greeting, was
recorded using ADPCM compression. If
you are running R1.1.0 or higher, you
must leave the compression format set to
ADPCM. The ability to select the format
allows you to migrate existing data into an
older database for backwards
compatibility.
In release R2.6 and all later releases, the
compression is set to ADPCM and you
cannot change it.
Caller ID
information is
not appearing
when an outside
call arrives.
Your local telephone
company is not
providing Caller ID
service to you.
Caller ID is typically an optional service
which you must order from your
telephone company.
You may be able to see caller ID by
number or by name (or both) depending
on the service your telephone company
provides.
You are answering
the telephone before
the Caller ID
information is fully
received.
Caller ID information does not appear
immediately. It usually appears between
the first and second rings. If you answer
the call too quickly, the information is
never received.
Table 36
Troubleshooting Actions (continued)
Symptom
Possible Cause
Suggested Action