Contents Of The Settings File - Avaya J100 Series Installing And Administering

Phone configuration

Contents of the settings file

The settings file can include any of the six types of statements, one per line:
• Tags, which are lines that begin with a single "#" character, followed by a single space
character, followed by 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 no such statement
exists, 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. The only parameters that can be used in a conditional statement are:
GROUP, MACADDR, MODEL and MODEL4.
• 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, if the value itself is numeric,
you must place the numeric value inside a pair of quotation marks. For example, "192.x.y.z"
• Comments, which are statements with characters "##" in the first column.
• GET commands, of the form GET filename. The phone attempts to download the file named
by filename, and if it is successfully obtained, it will be interpreted as an additional settings
file, and no additional lines will be interpreted in the original file. If the file cannot be obtained,
the phone will continue to interpret the original file.
The Avaya-provided upgrade file includes a line that tells the phones to GET 46xxsettings.txt.
This line cause the phone to use HTTP/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
phone continues processing the upgrade script file. Also, if the settings file is successfully
obtained but this does not change any settings, the phone continues to use HTTP.
The settings file is under your control and is where you can identify non-default option settings,
application-specific parameters, etc. You can download a template for this file from the Avaya
support Web site.
During a reboot, if the phone is unable to access the settings file, it does not retain the values of
all the parameters. For more information on which parameter value is retained, see the following
table.
Parameter
AGCHAND
AGCHEAD
AGCSPKR
APPNAME
AUDIOENV
AUDIOSTHD
AUDIOSTHS
July 2019
Retained
Y
Y
Y
N
N
N
N
Installing and Administering Avaya J100 Series IP Phones
Comments on this document? infodev@avaya.com
Table continues...
152