Avaya 1603SW Betriebsanweisung
1603SW-I SIP IP Deskphone Upgrade and Binary Files
Issue 1 June 2010
67
Table 10: Settings File System Parameters That Can Be Tested in an IF Statement
The 16xxupgrade.txt files distributed by Avaya start with a GOTO GETSET command based
on the value of the SIG parameter to preclude loading SIP software into a phone that has been
manually designated to run H.323 software (indicated by a SIG value of 1), and to preclude
loading H.323 software into a phone that has been manually designated to run SIP software
(indicated by a SIG value of 2). The default SIG value of zero indicates that the telephone
should download whatever software is available.
on the value of the SIG parameter to preclude loading SIP software into a phone that has been
manually designated to run H.323 software (indicated by a SIG value of 1), and to preclude
loading H.323 software into a phone that has been manually designated to run SIP software
(indicated by a SIG value of 2). The default SIG value of zero indicates that the telephone
should download whatever software is available.
The 16xxupgrade.txt files distributed by Avaya end with the statement GET 46xxsettings.txt.
If you need to redefine the values of any parameters for your installation, do so in the
46xxsettings.txt file and not in the 16xxupgrade.txt file. The reason for using the
46xxsettings.txt file is because each new Avaya release you download will include a new
version of 16xxupgrade.txt, which will overwrite any changes you have made to your previous
copy of that file.
If you need to redefine the values of any parameters for your installation, do so in the
46xxsettings.txt file and not in the 16xxupgrade.txt file. The reason for using the
46xxsettings.txt file is because each new Avaya release you download will include a new
version of 16xxupgrade.txt, which will overwrite any changes you have made to your previous
copy of that file.
Avaya recommends that you do not alter the 16xxupgrade.txt file. If Avaya changes the
16xxupgrade.txt 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
16xxupgrade.txt 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 16xxupgrade.txt file.
For more information on customizing your settings file, see
Contents of the Settings File
The final step in processing the 16xxupgrade.txt file is to GET the 46xxsettings.txt file. The
default 46xxsettings.txt file contains explanatory material and default values on lines that start
with ##. A parameter value can be changed and actioned by changing its value and removing
the two ##'s at the beginning of the line.
default 46xxsettings.txt file contains explanatory material and default values on lines that start
with ##. A parameter value can be changed and actioned by changing its value and removing
the two ##'s at the beginning of the line.
Parameter
Description
BOOTNAME
The name of the boot code file in the telephone.
MACADDR
MAC address of the phone (hh:hh:hh:hh:hh:hh; automatically supplied by a
phone).
phone).
MODEL
Telephone Model identifier (8 ASCII characters; automatically supplied by a
phone).
phone).
MODEL4
The first four digits of the model identifier (automatically supplied by a
phone).
phone).
PWBCC
Avaya identification number for the printed circuit board (automatically
supplied by a phone).
supplied by a phone).
GROUP
Group identifier (must be manually set on a phone)
SIG
Signalling protocol identifier (2=SIP, 1=H.323, 0=default; must be manually
changed on a phone).
changed on a phone).