Avaya 1603SW Guia Do Utilizador

Note:

Avaya recommends that the settings file have the extension *.txt. The Avaya IP 
Deskphones can use Avaya-provided default values and operate without this file 
if you have no settings you want to customize. Note that you can also change 
these settings with DHCP (for information see 

) or, in some cases, from the dialpad of the telephone using 

local administrative (Craft) procedures described in the Avaya one-X™ 
Deskphone Value Edition SIP for 1603SW-I IP Deskphones Installation and 
Maintenance Guide. 

Note:

Use one settings file for all your Avaya IP Deskphones. The settings file includes 
the 1603SW-I SIP IP Deskphones covered in this document. The settings file 
also includes parameters for 9600 Series (H.323) IP Telephones, 4600 Series IP 
Telephones, and 1600 Series IP Telephones as covered in their respective 
administrator guides.

The settings file can include five types of statements, one per line. Any invalid statement is 
ignored. The statement types are:

●

SET statements of the form SET parameter_name value. If the desired value contains a 
blank or a comma, the entire value must by placed within double quotes. 

●

GET statements of the form GET filename, which cause the phone to get the named file 
from the same file server and directory from which it got the current file. If the file is not 
available, the phone continues to execute the current file.

●

GOTO statements, of the form GOTO tag. GOTO statements cause the telephone to 
continue interpreting the configuration file after a line that begins with a “# tag” statement. 
If no such line exists in the upgrade or settings file after the GOTO, the phone ignores 
anything in the file after the GOTO.

●

Tags are lines that begin with a # tag; tag is an unquoted string and cannot contain a space 
or comma. 

●

IF statements, of the form IF $name SEQ string GOTO tag, where name is one of the 
system parameters shown in table #A#. Conditionals cause the GOTO command to be 
processed if the (string equivalent) value of name is equal to string. Note that the string 
comparison ignores case, so “Abc” matches “ABC” or “abc”. If no such name exists, the 
entire conditional is ignored. As for SET statements, the string must be included in double 
quotes if it includes spaces or commas. Any string may be double quotes, so 1 and “1” are 
equivalent as are “abc” and abc.

Any line which does not match one of the previous statement types is ignored and, therefore, 
can be treated as a comment. By convention, in the upgrade and settings files distributed by 
Avaya, any line intended to be ignored by the phone or read as a comment starts with “##”.