Avaya 3600 - Manual (Page 57)

Avaya, Inc. Configuration and Administration—AVAYA 3616/3620/3626 WT
Avaya CCMS IP, Avaya Call Server, with Avaya 4612 IP Telephone Emulation
21-300352, Issue 2, July 2005 Page 57
Message Description Action
Extension Error Displayed for 5 seconds when all of
the Call Servers contacted indicate
that they do not recognize the
current extension as valid. The user will be asked to enter a
valid extension and password
Extension in Use The phone is trying to register with
an extension that is already
registered on the Call Server. See Avaya Call Server Integration
Factors section.
Files Too Big WT software download files are
incorrect or corrupted Download new software from the
OEM site per Software
Maintenance.
Flash Config Error WT internal configuration is corrupt. Perform "Restore Defaults"
operation via administrator menus
[or reprogram with Configuration
Cradle]
Gatekeeper REJ Gatekeeper rejected Discovery
Request from the WT Check the H.323 gatekeeper
configuration in the WT.
Verify the gatekeeper or PBX’s
configuration
H225 Listen Fail WT cannot communicate with the AP
or the AVPP This message may display with
another diagnostic message.
Follow diagnostic actions for the
second message (such as No Net
Found).
H245 Listen fail WT cannot communicate with the AP
or the AVPP This message may display with
another diagnostic message.
Follow diagnostic actions for the
second message (such as No Net
Found).
Incompatible The switch is rejecting the software
version presented by the phone. If this condition persists, contact
the Avaya system administrator.
Initializing … The WT is performing power on
initialization None. This is informational only.
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)
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.
Invalid Revision Gatekeeper rejected registration
request from the WT Verify the gatekeeper or PBX’s
configuration. Ensure the
gatekeeper and PBX will support
version 2 of the H.323 protocol.