EasyManua.ls Logo

Avaya 9608 - Chapter 12: Receiving your messages; Logging into your voice mail

Avaya 9608
91 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Message Cause/Resolution
Limit Error
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.
NAPT Error
CAUSE: A device between the phone and the call server is invoking Network
address Port Translation (NAPT), which the 9600 Series IP phones do not
support.
RESOLUTION: Contact the System Administrator to remove or re-administer the
device.
No Ethernet
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.
Packet Error
CAUSE: Protocol timeout error.
RESOLUTION: Reenter the correct extension and password. If the condition
persists, contact the system administrator.
Password Error
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.
Request Error
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.
Restarting...
CAUSE: The phone is in the initial stage of rebooting.
RESOLUTION: Allow the phone boot process to continue.
Subnet conflict
* to program
CAUSE: The phone is not on the same VLAN subnet as the router.
RESOLUTION: Press star (*) to administer an IP address on the phone. For
information on configuring an IP address, see Changing IP address
information on page 44, or administer network equipment to administer the
phone appropriately.
System busy
CAUSE: Most likely, the number of IP endpoints on the call server is already at
maximum capacity. Network resource may not be unavailable.
RESOLUTION: The phone attempted to access a network resource such as
DHCP server, HTTP server, or the call server and was not successful. Check the
resource being called upon for its availability. If the resource appears operational
and is properly linked to the network, verify that the addressing is accurate and
that a communication path exists in both directions between the phone and the
resource.
System Error
CAUSE: The call server has an unspecified problem.
Table continues…
Troubleshooting
March 2018 Installing and Maintaining Avaya 9608/9608G/9611G/9621G/9641G/9641GS IP
Deskphones H.323 77
Comments on this document? infodev@avaya.com

Table of Contents

Other manuals for Avaya 9608

Related product manuals