The user hears echo on a
headset, but not on a handset.
Cause: Improper headset
adapter.
Resolution: Replace adapter with
Avaya’s M12LU or 3412-HIC
adapters. We recommend the
M12LU, since it supports
Automatic Gain Control.
The user is on Speaker and hears
no echo, but the far-end hears
echo.
Cause: Room acoustics.
Resolution: Ensure that there are
six inches or so of blank space to
the right of the phone. If that is
insufficient, use the handset.
the user experiences sudden
silences such as gaps in speech,
or static, clipped or garbled
speech, etc.
Cause: Jitter, delay, dropped
packets, etc.
Resolution: You can have the
user provide diagnostic data by
invoking the Network Information
feature under the A (Avaya)
button on the phone. One or more
Quality of Service (QoS) features
should be implemented in the
network.
Cause: Improper non-Category 5
wiring.
Resolution: Replace non-
Category 5 wiring with Category 5
wiring.
The user hears fluctuations in the
volume level which are worse
when the Speaker is on, or at the
beginning of a call, or when a call
goes from no one talking abruptly
to a loud voice.
Cause: The user has changed the
Automatic Gain Control (AGC) or
environmental acoustics are not
consistent with the current audio
settings.
Resolution: Try different on/off
settings for the AGCHAND,
AGCHEAD, and AGCSPKR
parameters.
The phone works properly except
for the Speaker.
Cause: The Speaker was disabled in the settings file.
Resolution: Check the settings file and re-enable the Speaker if
appropriate.
The phone works properly, except
incoming DTMF tones are not
received.
Cause: The TN2302AP board does not pass in-band DTMF tones.
Resolution: None; the board is operating as designed.
Table continues…
Operational errors and status messages
January 2020 Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP 147
Comments on this document? infodev@avaya.com
To Next Page
Loading...
