Previous page Next page

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.

In Table 18, 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 Table 16:  Possible Error Messages During Installation or Operation of 4600 Series IP Telephones. However, rather than displaying messages, the 4601 turns its LEDs on and off to indicate an error condition, as described in Table 18’s second column. In addition, not all error conditions result in unique LED indications.

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.
Extension
in Use
VISUAL INDICATION: If the extension is being used, the 4601 attempts registration. The first attempt causes the Message Waiting indicators at the top of telephone and left middle of the faceplate to display a broken flutter. The broken flutter alternates 50 milliseconds on, 50 milliseconds off for 500 milliseconds, followed by 500 milliseconds off five times. Then the indicators flash continuously, awaiting user entry. Then the 4601 makes a second registration attempt using the same extension. This attempt causes the Message Waiting indicators at the top of telephone and left middle of the faceplate to display a continuous broken flutter. The broken flutter alternates 50 milliseconds on, 50 milliseconds off for 500 milliseconds followed by 500 milliseconds off. In addition, Call Appearance Line b’s LED flashes continuously until either the “*” or “#” button is pressed.
CAUSE: The PBX detects an extension conflict with an existing set or Softphone.
RESOLUTION: You can force the current telephone to register, and thereby disconnect the other user, by pressing #. The 4600 Series IP Telephone prompts you again for the extension and password. If you enter the same extension and password, you must confirm that you want to unregister the original user. Press # to unregister the original user and register the current telephone. Then press * to reset the telephone and enter a different extension and password. If you take no action within 20 minutes, the telephone attempts registration again, repeating the process until either you intervene or power is lost.
IP Address in use by another
VISUAL INDICATION: All LEDs are steadily lit, except Call Appearance Line A, which is flashing.
CAUSE: The telephone has detected an IP Address conflict.
RESOLUTION: DHCP restart is automatically initiated. No user action required.
No Ethernet
VISUAL INDICATION: No LEDs flash when telephone is plugged in.
CAUSE: Telephone is unable to communicate with the Ethernet.
RESOLUTION: Verify the connection to the Ethernet jack, verify the jack is Category 5, verify power is applied on the LAN to that jack, etc.
Password Error
VISUAL INDICATION: Message Waiting indicators at top of telephone and left middle of 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), then flash continuously, awaiting user entry.
CAUSE: The PBX does not recognize the password entered.
RESOLUTION: Confirm the password is correct, then try registration again, taking particular care to enter the password accurately.
System busy
VISUAL INDICATION: Message Waiting indicators at top of telephone and left middle of faceplate display a broken flutter continuously (alternating 50 milliseconds on, 50 milliseconds off for 500 milliseconds followed by 500 milliseconds off) until either the “*” or “#” button is pressed.
CAUSE: Most likely, the number of IP endpoints on the PBX is already at maximum, Less likely, network resource is unavailable.
RESOLUTION: The telephone was attempting to access the PBX and was not successful. Check the resource being called upon for availability. If the resource appears operational and properly linked to the network, verify addressing is accurate and that a two-way telephone/resource communication path exists. Press * to retry the process with the same values, or # to restart and enter the extension and password again.
System Error
VISUAL INDICATION: Message Waiting indicators at top of telephone and left middle of faceplate display a broken flutter continuously (alternating 50 milliseconds on, 50 milliseconds off for 500 milliseconds followed by 500 milliseconds off) until either the “*” or “#” button is pressed.
CAUSE: The PBX has an unspecified problem.
RESOLUTION: Press * to retry the process using the same values
or # to restart and re-enter the extension and password. Consult your Avaya Media Server administration and troubleshooting documentation.
Undefined Error
VISUAL INDICATION: Message Waiting indicators at top of telephone and left middle of faceplate display a broken flutter continuously (alternating 50 milliseconds on, 50 milliseconds off for 500 milliseconds followed by 500 milliseconds off) until either the “*” or “#” button is pressed.
CAUSE: The PBX has rejected registration for an unspecified reason.
RESOLUTION: Press * to retry the process using the same values or # to restart and re-enter the extension and password. Consult your Avaya Media Server administration and troubleshooting documentation.
Wrong Set Type
VISUAL INDICATION: Message Waiting indicators at top of telephone and left middle of faceplate display a broken flutter continuously (alternating 50 milliseconds on, 50 milliseconds off for 500 milliseconds followed by 500 milliseconds off) until either the “*” or “#” button is pressed.
CAUSE: The PBX does not recognize the set type.
RESOLUTION: Ensure the PBX is properly administered to expect the appropriate telephone for the IP Address and extension. Press * to retry the process using the same values or # to restart and re-enter the extension and password.


Previous page Next page