Avaya 4600 Manuel D’Utilisation

Page de 178
Troubleshooting Guidelines
148 4600 Series IP Telephone LAN Administrator Guide
 
Troubleshooting the 4601 IP Telephone
This section describes specific problems that can occur during 4601 IP Telephone installation, 
administration or normal operation, and possible ways of resolving these problems.
, the Error Messages shown in the first column correspond to the equivalent 
conditions described in “Chapter 4" of the 4600 Series IP Telephone Installation Guide and 
. However, rather than displaying messages, the 4601 turns its LEDs on and off to 
indicate an error condition, as described in 
s second column. In addition, not all error 
conditions result in unique LED indications.
Table 17: Possible Error Messages During 4610SW, 4620/4620SW, 4621SW, 4622SW, 
4625SW, and 4630/4630SW Backup/Restore 
Error Message
Cause/Resolution
The FTP Server has 
denied access 
Please check FTP 
Setup parameters
 
CAUSE: The FTP server has reported that it did not store data.
RESOLUTION: Verify the FTP server setup parameters, as 
indicated on the FTP Setup Parameters screen. See “FTP Setup” 
in Chapter 8 of the 4630/4630SW IP Telephone User Guide, or 
see “Backup/Restore Options” in Chapter 6 of the appropriate 
User Guide for the telephone type. 
The FTP Server was 
unable to store the 
backup file
 
CAUSE: The FTP server has reported that it could not store the 
data.
RESOLUTION: Verify administration and available capacity/
filespace on the FTP server.
Table 18: Possible Error Messages During 4601 IP Telephone Installation or 
Operation 
Error Message
4601 Visual Indication/Cause/Resolution
Extension 
Error
 
VISUAL INDICATION: Message Waiting indicators at top of telephone and 
the left middle of the faceplate display a broken flutter for a total of 5 cycles 
(with one cycle being alternating 50 milliseconds on, 50 milliseconds off for 
500 milliseconds followed by 500 milliseconds off). 
CAUSE: The PBX does not recognize the extension entered or cannot find 
a valid gatekeeper.
RESOLUTION: Confirm the extension is correct and is correctly 
administered on the switch. Then try registration again, taking particular 
care to enter the extension accurately. 
1 of 3