Avaya 4600 Manual Do Utilizador

The TFTP or HTTP 
script file is ignored 
or not used by the 
telephone 

AND the TFTP or 
HTTP server is a 
LINUX or UNIX 
system.

CAUSE: The telephone expects lines of the 
script file to terminate with a 

. Some UNIX 

applications only terminate lines with 

. Editing the script file with a 

UNIX-based editor can strip 

s from the file. Doing so causes the 

entire file to be treated as a comment, and 
thus be ignored. 
RESOLUTION: Edit the script file with a 
Windows

®

-based editor, or another editor 

that does not strip out the 

. 

CAUSE: UNIX and LINUX systems use 
case-sensitive addressing and file labels. 
RESOLUTION: Verify the file names and 
path in the script file are accurately specified. 

AND telephone 
administration recently 
changed.

CAUSE: The 46xxupgrade.scr file was 
mis-edited, renamed, etc.
RESOLUTION: Download a clean copy of 
the 46xxupgrade.scr file from the Avaya 
support Web site, and do not edit or rename 
it. Customize or change only the 
46xxsettings file, as discussed in 

. 

Telephone power is interrupted while the 
telephone is saving the application file and the 
TFTP or HTTP application stops responding.

CAUSE: The TFTP or HTTP server stops 
responding if power is interrupted while a 
telephone is saving the application file.
RESOLUTION: Restart the TFTP or HTTP 
server, as applicable.

The DHCP server indicates the 4600 Series IP 
Telephone reports itself as a Token Ring 
device, and refuses to provide the telephone 
an address.

CAUSE: Early versions of the 4600 Series IP 
Telephones erroneously report being a 
Token Ring device. With most DHCP 
servers, this does not matter. Some LINUX 
servers, however, refuse to issue addresses 
to Ethernet devices reporting to be Token 
Ring devices.
RESOLUTION: Administer the DHCP server 
to delete all MAC and IP Addresses 
associated with Lucent Technologies or 
Avaya, or allow the associated DHCP leases 
to expire.