When a line is selected, a short
dial tone burst sounds followed by
a reorder/fast busy tone.
Cause: The extension is provisioned on Session Manager and some
Communication Manager forms, but not on the off-pbx-telephone
station-mapping form. Communication Manager is unable to map
back to Session Manager, and rejects the line reservation.
Resolution: Map the extension on the off-pbx-telephone station-
mapping form.
Cause: Possible error in SIG group configuration on Communication
Manager, which indicates the default region for the SIP trunk to
Communication Manager.
Resolution: On the IP-network-region form, ensure that the region
pointed to is configured with an authoritative domain that is the
same as the Session Manager SIP domain. also verify that the station
in question has not been redirected to a different network region on
the ip-network map.
The HTTP/HTTPS script file and
settings file are ignored (not being
used by the phone).
Cause: The system value AUTH is set to 1 (HTTPS required) but no
valid address is specified in TLSSRVR.
Resolution: Change AUTH to 0 (zero), or enter a valid address for
TLSSRVR.
The HTTP/HTTPS script file is
ignored or not used by the phone.
The HTTP/ HTTPS server is a
LINUX or UNIX system.
Cause: UNIX and LINUX systems
use case-sensitive addressing
and file labels.
Resolution: Verify the file names
and path in the script file are
accurately specified.
The phone administration recently
changed.
Cause: The 96x1Supgrade.txtfile
was edited incorrectly, renamed,
etc.
Resolution: Download a clean
copy of the 96x1Supgrade.txt file
from the
Avaya support siteand
do not edit or rename it.
Customize or change only the
46xxsettings file.
The MS Exchange contacts take
too long to load
Cause: The correct Exchange server is not specified in the parameter
EXCHANGE_SERVER_LIST in the 46xxsettings file.
Resolution: Verify that the MS Exchange server being used is
specified in the settings file. To view the Exchange server in use, go
to: Outlook > Tools>Options > Mail Setup > E-mail Accounts >
Change .
Some settings in the settings file
are being ignored while other
settings are being used properly.
Cause: Improper settings file administration.
Resolution: Verify that customized settings are correctly spelled and
formatted.
Table continues…
Troubleshooting
January 2020 Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP 148
Comments on this document? infodev@avaya.com