Avaya 4600 Manual Do Utilizador

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.

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 

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.