|
|
|
The 4600 Series IP Telephones issue messages in English only. The IP telephones also display messages from the switch, which outside the United States might issue messages in the local language.
NOTE: Because the 4601 IP Telephone does not have a display, it is limited in its ability to provide visual feedback and error messages. Nonetheless, some feedback is available and presented as applicable. For more information, see Table 18: Possible Error Messages During 4601 IP Telephone Installation or Operation.
| Error Message |
Cause/Resolution |
|---|---|
| During Installation |
|
| Bad Router |
CAUSE: The telephone cannot find a router based on the information in the DHCP file for GIPADD. RESOLUTION: Change administration on DHCP, as indicated in DHCP in Chapter 4: Server Administration. |
| Checksum error |
CAUSE: Downloaded application file was not downloaded or saved correctly. RESOLUTION: The telephone automatically resets and attempts to re-initialize. |
| DHCP: CONFLICT * to program |
CAUSE: At least one of the IP Address offered by the DHCP server conflicts with another address. RESOLUTION: Review DHCP server administration to identify duplicate IP Address(es). |
| Discover aaa.bbb.ccc.ddd |
CAUSE: The 46xx telephone is attempting to discover (and register with) the Gatekeeper at IP Address aaa.bbb.ccc.ddd. RESOLUTION: If this message appears for more than a few seconds, especially if the IP Address keeps changing, the telephone is unable to contact the Gatekeeper. Verify network connectivity between the telephone and the Gatekeeper, or revise the Gatekeeper addresses in the DHCP/script files to point to different Gatekeepers. See Administering 4600 Series IP Telephones on Avaya Media Servers (H.323 Only), DHCP, TFTP (H.323 Only), and HTTP. |
| Discovering... |
CAUSE: The telephone is seeking a gatekeeper on the media server, using its administered gatekeeper list. RESOLUTION: Wait for a valid registration to occur, or press # to interrupt the search and re-initialize manual or DHCP/script files procedures. |
| File too large Cannot save file |
CAUSE: The telephone does not have sufficient room to store the downloaded file. RESOLUTION: Verify the proper filename is administered in the script file, and that the proper application file is located in the appropriate location on the file server. |
| Gateway Error |
CAUSE: DEFINITY Release 8.4 does not have an H.323 station extension for this telephone. RESOLUTION: On the station administration screen, ensure the DCP set being aliased for this IP telephone has an H.323 station extension administered, in accordance with switch administration instructions. |
| Hardware failure |
CAUSE: Hardware failure prevented downloading of application file. RESOLUTION: Replace telephone. |
| IP Address in use by another |
CAUSE: The telephone has detected an IP Address conflict. RESOLUTION: Verify administration to identify duplicate IP Address(es). |
| NAPT Error |
CAUSE: A device between the telephone and the call server is invoking Network Address Port Translation, which the 4600 Series IP Telephones do not support. RESOLUTION: Remove or re-administer the NAPT device or move the telephone. |
| No Ethernet |
CAUSE: When first plugged in, the IP telephone is unable to communicate with the Ethernet. RESOLUTION: Verify the connection to the Ethernet jack, verify the jack is Category 5, etc. Note that if the telephone is attached to a 30A switched hub, upon loss of Ethernet connectivity, the usual “No Ethernet” message is not displayed. |
| No file server address |
CAUSE: The file server IP Address in the IP telephone’s memory is all zeroes. RESOLUTION: Depending on the specific requirements of your network, this may not be an error. If appropriate, either administer the DHCP server with the proper address of the file server, or administer the telephone locally using the ADDR option. The 4600 Series IP Telephone Installation Guide explains the ADDR option. |
| No Socket |
CAUSE: The telephone has registered with the call server, but network problems have prevented the telephone from opening a TCP socket. Note: This message only occurs on older software versions. Telephones with newer software automatically reset. RESOLUTION: Investigate the network problem normally. |
| System busy |
CAUSE: Most likely, the number of IP endpoints on the Avaya Media Server is already at maximum, Less likely, network resource is unavailable. RESOLUTION: The telephone was attempting to access a network resource (DHCP server, TFTP server, or the Avaya Media Server) and was not successful. Check the resource being called upon for its availability. If the resource appears operational and properly linked to the network, verify addressing is accurate and a communication path exists in both directions between the telephone and the resource. |
| System Error |
CAUSE: The Avaya Media Server has an unspecified problem. RESOLUTION: Consult your Avaya Media Server administration and troubleshooting documentation. |
| During Registration |
|
| Bad Router |
CAUSE: The telephone cannot find a router based on the information in the DHCP file for GIPADD. RESOLUTION: Change administration on DHCP, as indicated in DHCP in Chapter 4: Server Administration. |
| Extension error |
CAUSE: An invalid Avaya Media Server Registration extension has been entered. RESOLUTION: Reenter the extension if entered incorrectly. If appropriate, verify proper extension with respect to switch administration. |
| Extension in use |
CAUSE: The specified extension is already in use, according to the Avaya Media Server. RESOLUTION: You will be told if the telephone using the same extension is on a call or not. Regardless, you can proceed to take over the extension or to login using a different extension. Telephones with large displays, such as the 4610SW or 4625SW, and Release 2.7 software provide detailed messages and specially labeled softkeys to guide you through either alternative. If the telephone has a two-line display, or does not support Release 2.7, you can either press the # key twice to take over the extension and log the other telephone off or you can press #, then * to enter a different extension. |
| Failed to set phone IP Address |
CAUSE: The 4600 Series Telephone was originally installed on one switch with Static Addressing, and has subsequently been installed on another switch with an active DHCP server assigning dynamic IP Addresses. RESOLUTION: Reset the telephone. |
| Incompatible |
CAUSE: This release of the Avaya Media Server does not support the current version of the IP telephone. RESOLUTION: Upgrade to the current version of Avaya Media Server software. |
| IP Address Error |
CAUSE: The gatekeeper reports an invalid IP Address. RESOLUTION: This should never happen. Contact Avaya. |
| Message light blinks on and off, and the telephone did not complete registration |
CAUSE: The telephone has a hardware fault. RESOLUTION: Replace the telephone. |
| NAPT Error |
CAUSE: A device between the telephone and the call server is invoking Network Address Port Translation, which the 4600 Series IP Telephones do not support. RESOLUTION: Contact the System Administrator to remove or re-administer the NAPT device. |
| No Call Server Address - Resetting |
CAUSE: The system parameter MCIPADD does not contain at least one non-zero IP Address or DNS Name, causing the telephone to reset. RESOLUTION: Add the IP Address(es) using static addressing (manual telephone setting), updating the settings file, or normally through DHCP administration. |
| No Proxy Found (SIP only) |
CAUSE: A problem with the list of SIP registration/proxy servers. RESOLUTION: Review the server administration to ensure that the correct addresses are specified. Verify the proper operation of the Registration Server(s) and the intervening network. |
| No Socket |
CAUSE: The telephone has registered with the call server, but network problems have prevented the telephone from opening a TCP socket. Note: This message only occurs on older software versions. Telephones with newer software automatically reset. RESOLUTION: Press the # button to reset the telephone and contact the [Network] System Administrator to report the network problem. |
| Password Error |
CAUSE: An invalid PBX Registration password has been entered. RESOLUTION: Re-enter the password if entered incorrectly. If appropriate, verify proper password with respect to switch administration. |
| Registering... (SIP only) |
CAUSE: It is normal for this message to occasionally appear for a short time. If the message appears for an extended time period, the telephone is unable to register. RESOLUTION: Verify proper operation of the Registration Server(s) and the intervening network. |
| Registration Failed (SIP only) |
CAUSE: The registration process failed. RESOLUTION: Verify the proper operation/administration of the Registration Server(s) and the intervening network. |
| Resource Error |
CAUSE: The Avaya Media Server rejects the registration request. RESOLUTION: Verify your Avaya Media Server administration to ensure the telephone’s proper IP Address, extension, and password are being used. |
| Timeout Error |
CAUSE: Protocol timeout error. RESOLUTION: Retry. If failure continues, check network congestion, addresses, etc. to identify cause of timeout. |
| Unauthorized (SIP only) |
CAUSE: The Registration Server does not recognize the extension and password. RESOLUTION: Reenter the correct extension and password. If the problem persists, contact the System Administrator. |
| Undefined Error |
CAUSE: An error has occurred without an identifiable cause. RESOLUTION: Conduct self-test, restart the telephone, and if no other cause becomes evident, replace the telephone. |
| Wrong Set Type |
CAUSE: The Avaya Media Server does not recognize the set type. RESOLUTION: Ensure that the Avaya Media Server is properly administered to expect the appropriate telephones for the IP Address and extension. |
| During Operation |
|
| Discover aaa.bbb.ccc.ddd |
CAUSE: The 46xx telephone is attempting to discover (and register with) the Gatekeeper at IP Address aaa.bbb.ccc.ddd. RESOLUTION: If this message appears for more than a few seconds, especially if the IP Address keeps changing, the telephone is unable to contact the Gatekeeper. Verify network connectivity between the telephone and the Gatekeeper, or revise the Gatekeeper addresses in the DHCP/script files to point to different Gatekeepers. See Administering 4600 Series IP Telephones on Avaya Media Servers (H.323 Only), DHCP, TFTP (H.323 Only), and HTTP. |
| Discovering... |
CAUSE: The user is on a call when the network connection between the telephone and call server is interrupted, but the call stays connected. The telephone automatically starts procedures to register with the call server again. However, until registration succeeds, the user has no access to Avaya Communication Manager features and functionality. This message alerts users to the lack of connection to the call server. RESOLUTION: This is the same message, with the same implications and Resolution as the Discovering... message on page 137. |
| Current options and Speed Dial entries have not yet been backed up |
CAUSE: An attempt to save the current options and Speed Dial entries on the FTP server has not yet been made or is in progress. RESOLUTION: Wait for a message stating that backup was successful. |
| The FTP Server Name is not known. Please check the FTP Server IP Address |
CAUSE: Invalid or missing server name. RESOLUTION: Verify the FTPSRVR address is the file server to which backup data should be saved. Verify that the FTPDIR value is the correct directory path for that file server. |
| The FTP Server has not yet responded, so backup has not yet succeeded |
CAUSE: The FTP server has not responded to the attempt to backup/restore. RESOLUTION: Try again, verify the FTP server address, verify the FTP server is online, and/or verify the network connectivity. |
|
|
|