Avaya napt error

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.

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/TFTP files (see Administering 4600 Series IP Telephones on Avaya Media Servers, DHCP, and TFTP) to point to different Gatekeepers.

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/TFTP 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 TFTP script file, and that the proper application file is located in the appropriate location on the TFTP 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 TFTP 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 TFTP server, or administer the telephone locally using the ADDR option as detailed in the 4600 Series IP Telephone Installation Guide.

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. The resource being called upon should be checked for its availability. If it 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.

Extension error

CAUSE: An invalid Avaya media server Registration extension has been entered.

RESOLUTION: Re-enter the extension if mis-entered initially. 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: Wait a few minutes, and try again. This will work for the case when the extension is correctly administered, but service was interrupted and the Avaya media server is not yet aware of that fact. Otherwise, verify proper extension with respect to switch administration.

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.

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 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 mis-entered initially. If appropriate, verify proper password with respect to switch administration.

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.

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 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/TFTP files (see Administering 4600 Series IP Telephones on Avaya Media Servers, DHCP, and TFTP) to point to different Gatekeepers.

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 initiates procedures to re-register with the call server, but 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 90.

Troubleshooting

Message

Incompatible

Invalid file

IP address Error

License Error

Limit Error

NAPT Error

No Ethernet

Packet Error

Password Error

Request Error

Restarting…

May 2018

Cause/Resolution

supported on DEFINITY Release 8.4, you must upgrade to a release that

supports these phones.

CAUSE: This release of the call server does not support the current version of

the IP phone.

RESOLUTION: Upgrade to the current version of Communication Manager (3.0

or greater) software.

CAUSE: The phone does not have sufficient room to store the downloaded file.

RESOLUTION: Verify that the proper filename is administered in the script file,

and the correct application file is located in the appropriate location on the HTTP

or HTTPS server.

CAUSE: The gatekeeper reports an invalid IP address.

RESOLUTION: This must not happen. Contact Avaya support.

CAUSE: The call server does not support IP telephony.

RESOLUTION: Contact Avaya to upgrade your license.

CAUSE: The call server has reached its limit of IP stations.

RESOLUTION: Un-register phones that are not in use, or contact Avaya to

upgrade your license.

CAUSE: A device between the phone and the call server is invoking Network

address Port Translation (NAPT), which the phone do not support.

RESOLUTION: Contact the System Administrator to remove or re-administer the

device.

CAUSE: When first plugged in, the IP phone is unable to communicate with the

Ethernet.

RESOLUTION: Verify the connection to the Ethernet jack, verify if the jack is

Category 5, verify if power is applied on the LAN to that jack.

CAUSE: Protocol timeout error.

RESOLUTION: Reenter the correct extension and password. If the condition

persists, contact the system administrator.

CAUSE: The call server does not recognize the password entered and displays

the Login Error screen.

RESOLUTION: Confirm whether the password is correct, then try registering

again, and enter the password accurately.

CAUSE: The gatekeeper does not accept the registration request sent by the

phone as the request is not formatted properly.

RESOLUTION: The phone will automatically attempt to register with the next

gatekeeper on its list. If the problem persists, reboot the phone.

CAUSE: The phone is in the initial stage of rebooting.

RESOLUTION: Allow the phone boot process to continue.

Installing and Administering Avaya J169/J179 IP Phone H.323

Comments on this document? infodev@avaya.com

Table continues…

190

Troubleshooting Guidelines

116 4600 Series IP Telephone Release 2.2 LAN Administrator Guide

Extension in use

CAUSE: The specified extension is already in use, 
according to the Avaya media server.
RESOLUTION: Wait a few minutes, and try again. Waiting 
works when the extension is correctly administered, but a 
service interruption occurs of which the Avaya media 
server is not yet aware. Otherwise, verify the proper 
extension with respect to switch administration. 
Alternatively, if you are logging in from a remote location 
and want to log the other user off, press the # key twice, 
once at each prompt.

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.

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 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.

Table 12: Possible Error Messages During Installation or Operation of 4600 Series IP 
Telephones  (continued)

Error Message

Cause/Resolution

4 of 5

Join Tek-Tips^® Today!

Join your peers on the Internet’s largest technical computer professional community.
It’s easy to join and it’s free.

Here’s Why Members Love Tek-Tips Forums:

• Talk To Other Members
• Notification Of Responses To Questions
• Favorite Forums One Click Access
• Keyword Search Of All Posts, And More…

Register now while it’s still free!

Already a member? Close this window and log in.

Join Us             Close