3Com NBX 100 Administrator's Manual page 362

362 C 10: T
HAPTER ROUBLESHOOTING
Table 78 Troubleshooting Actions (continued)
Symptom Possible Cause
NBX NetSet is Your network uses a
very slow in proxy server for
responding. Internet access.
All greetings and The wrong message
prompts are compression format
missing. For was selected.
example, calling
the Auto
Attendant or a
user's mailbox
produces silence
instead of the
expected
greetings.
Caller ID Your local telephone
information is company is not
not appearing providing Caller ID
when an outside service to you.
call arrives.
You are answering
the telephone before
the Caller ID
information is fully
received.
Suggested Action
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.
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 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.
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. If you transfer the call, the
person you transfer the call to sees your
ID instead of the ID of the original caller.