Contents of the settings file

Last Updated : Aug 28, 2026 |
Prolog information
Metadata
Keywords:
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.
    Important:
    There must be space character between # and tag.
  • 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.
  • Conditionals of the form IFstring1 SEQstring2 GOTOtag. Conditionals cause the Goto command to be processed if the value of string1 exactly matches the value of string2. string1 or string2 can be defined using a macro: $GROUP, $MACADDR, $MODEL and $MODEL4. For example: If $MODEL4 SEQ J179 GOTO J179_CONFIG. When Avaya J179 IP Phone encounters this line, it goes to tag # 179_CONFIG. When other phones encounter this line, its ignored.
  • 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.
    Note:
    A filename can be a macro: $GROUP, $MACADDR, $MODEL, and $MODEL4. For example: GET $MACADDR.txt. Avaya J100 Series IP Phones attempts to perform a GET of the device MAC address.txt such as c81feaddeeff.txt.
The Avaya-provided upgrade file includes a line that tells the phones to GET46xxsettings.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 Website.
When Avaya J100 Series IP Phones is in the process of downloading configuration from the provisioning server, the phone does one of the following:
  • If the phone is unable to download the J100Supgrade.txt file then all previously downloaded configuration is cached.
  • If the phone is able to download the J100Supgrade.txt file then all previously downloaded configuration is cleared.
    • If the phone is able to download the subsequent 46xxsettings.txt file then the configuration is re-applied.
    • If the phone is unable to download the subsequent 46xxsettings.txt file then the previously downloaded configuration is cleared.
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
Retained
AGCHAND
Y
AGCHEAD
Y
AGCSPKR
Y
APPNAME
N
AUDIOENV
N
AUDIOSTHD
N
AUDIOSTHS
N
AUTH
Y
BAKLIGHTOFF
Y
CNGLABEL
Y
DAYLIGHT_SAVING_SET TING_MODE
Y
DHCPSTD
N
HEADSYS
N
HOMEIDLETIME
N
LOG_CATEGORY
Y
LOGSRVR
N
LOCAL_LOG_LEVEL
Y
LANG0STAT
Y
MSGNUM
N
PROCSTAT
Y
PROCPSWD
Y
PHY1STAT
Y
PHY2STAT
Y
PHNCC
N
PHNDPLENGTH
N
PHNIC
N
PHNLDLENGTH
N
PHNLD
N
PHNLAC
Y
PHNOL
N
RFSNAME
N
SNMPADD
Y
SNMPSTRING
Y
SIG
Y
SCREENSAVERON
N
TEAM_BUTTON_RING_T YPE
Y
TPSLIST
N
VLANTEST
Y
WMLHOME
N
WMLPORT
N
WMLPROXY
N
Related linksOverview of the 46xxsettings.txt file