1600 Series IP Telephone Scripts and Application Files
Settings File
The settings file contains the option settings you need to customize the Avaya IP Telephones for your enterprise.
Note:
You can use one settings file for all your Avaya IP Telephones. The settings file includes the 1600 Series IP Telephones covered in this document as well as 9600 Series IP Telephones and 4600 Series IP Telephones.
The settings file can include any of five types of statements, one per line:
●Comments, which are statements with a “#” character in the first column.
●Tags, which are comments that have exactly one space character after the initial #, followed by a text string with no spaces.
●Goto commands, of the form GOTO tag. Goto commands cause the telephone to continue interpreting the configuration file at the next line after a # tag statement. If no such statement exists, the rest of the configuration file is ignored.
●Conditionals, of the form IF $name SEQ string GOTO tag. Conditionals cause the Goto command to be processed if the value of name is a
●SET commands, of the form SET parameter_name value. Invalid values cause the specified value to be ignored for the associated parameter_name so the default or previously administered value is retained. All values must be text strings, even if the value itself is numeric, a dotted decimal IP address, and so on.
Note:
Enclose all data in quotation marks for proper interpretation.
The upgrade script file Avaya provides includes a line that tell the telephone to GET 46xxsettings.txt. This lines causes the telephone to use HTTP or HTTPS to attempt to download the file specified in the GET command. If the file is obtained, its contents are interpreted as an additional script file. That is how your settings are changed from the default settings. If the file cannot be obtained, the telephone continues processing the upgrade script file.
If the configuration file is successfully obtained but does not include any setting changes the telephone stops using HTTP. This happens when you initially download the script file template from the Avaya support Web site, before you make any changes. When the configuration file contains no setting changes, the telephone does not go back to the upgrade script file.
Avaya recommends that you do not alter the upgrade script file. If Avaya changes the upgrade script file in the future, any changes you have made will be lost. Avaya recommends that you use the 46xxsettings file to customize your settings instead. However, you can change the settings file name, if desired, as long as you also edit the corresponding GET command in the upgrade script file.
For more information on customizing your settings file, see Contents of the Settings File.
Issue 5 April 2010 63
