User's Manual

Contents of the settings file
The settings file can include any of six types of statements, one per line:
• Tags that are lines that begin with a single pound (#) character followed by a single space
character and a text string with no spaces.
• Goto commands, of the form GOTO tag. Goto commands cause the phone to continue
interpreting the settings file at the next line after a #tag statement. If such a statement
does not exist, the rest of the settings file is ignored.
• Conditionals, of the form IF $parameter_name SEQ string GOTO tag. Conditionals
cause the Goto command to be processed if the value of the parameter named
parameter_name exactly matches string. If no such parameter named parameter_name
exists, the entire conditional is ignored. You can use the following parameters in a
conditional statement: GROUP, MACADDR, MODEL and MODEL4.
• SET commands, of the form SET parameter_name value. The system ignores any
invalid values 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 or a dotted decimal IP Address.
• Comments, which are statements with a pound (#) character in the first column.
Note:
Enclose all data in quotation marks for proper interpretation.
• GET commands, of the form GET filename . If the phone downloads the file named as
filename, the phone interprets the file as an additional settings file and does not interpret
additional lines in the original file. If the phone cannot obtain the file, the telephone
continues to interpret the original file.
The Avaya-provided upgrade file includes lines that direct the phone to GET
46xxsettings.txt and 46xxsettings.scr. These lines cause the phone to use HTTP/
HTTPS to attempt to download the file specified in the GET command. If the phone obtains the
file, its contents are interpreted as an additional script file. If the file cannot be obtained, the
phone continues processing the upgrade script file. The phone processes the upgrade script
file so that if there is no 46xxsettings.scr file, the phone looks for a 46xxsettings.txt file. If the
phone obtains the settings file successfully but does not include any setting changes the phone
stops using HTTP. This process happens when you initially download the script file template
from the Avaya support Web site, before you make any changes. When the settings file
contains no setting changes, the phone does not go back to the upgrade script file.
You can customize the settings file and identify non-default option settings, application-specific
parameters, and other settings. You can download a template for this file from the
Avaya
Support website.
Contents of the settings file
Installing and maintaining Avaya B189 Conference IP Phone January 2014 23