Avaya 3600 Series Configuration And Administration Manual page 57

Avaya, Inc.
Message
Extension Error Displayed for 5 seconds when all of
the Call Servers contacted indicate
that they do not recognize the
current extension as valid.
Extension in Use The phone is trying to register with
an extension that is already
registered on the Call Server.
Files Too Big WT software download files are
incorrect or corrupted
Flash Config Error WT internal configuration is corrupt.
Gatekeeper REJ Gatekeeper rejected Discovery
Request from the WT
H225 Listen Fail WT cannot communicate with the AP
or the AVPP
H245 Listen fail WT cannot communicate with the AP
or the AVPP
Incompatible The switch is rejecting the software
version presented by the phone.
Initializing ... The WT is performing power on
initialization
Internal Err. # # The WT has detected a fault from
which it cannot recover.
OE = Error while writing the Flash
(return WT to factory)
OF = No functional code (contact
OEM Technical Support)
Invalid Revision Gatekeeper rejected registration
request from the WT
21-300352, Issue 2, July 2005
Configuration and Administration—AVAYA 3616/3620/3626 WT
Avaya CCMS IP, Avaya Call Server, with Avaya 4612 IP Telephone Emulation
Description Action
The user will be asked to enter a
valid extension and password
See Avaya Call Server Integration
Factors section.
Download new software from the
OEM site per Software
Maintenance.
Perform "Restore Defaults"
operation via administrator menus
[or reprogram with Configuration
Cradle]
Check the H.323 gatekeeper
configuration in the WT.
Verify the gatekeeper or PBX's
configuration
This message may display with
another diagnostic message.
Follow diagnostic actions for the
second message (such as No Net
Found).
This message may display with
another diagnostic message.
Follow diagnostic actions for the
second message (such as No Net
Found).
If this condition persists, contact
the Avaya system administrator.
None. This is informational only.
Record the error code so it can be
reported.
Turn the WT off then on again.
If error persists, try registering a
different WT to this telephone port.
If error still persists, contact OEM
Technical Support and report the
error.
Verify the gatekeeper or PBX's
configuration. Ensure the
gatekeeper and PBX will support
version 2 of the H.323 protocol.
Page 57