96x1H-IPI.2.1.500: Persistent parameters that cannot be set via DHCP or a configuration file |
Approved
|
The following persistent parameters will be initialized to the specified default values, will not be settable via DHCP or a configuration file, and will not be testable via an IF command in a configuration file.
|
Note:
|
These are “internal” parameters that cannot be set directly by name via DHCP or in a configuration file, and since they are not testable, the value can only be determined if it is displayed or if it is exposed in a MIB object. These parameter names are primarily specified to make it easier to refer to the value that they represent when specifying some aspect of telephone operation.
|
|
Persistent Parameter Name
and
(default value)
|
Valid Values
|
Notes
(usage and references)
|
|
APPINUSE
(see Valid Values)
|
The name of the Signed Application/Library Software Package installed in the telephone, with a maximum length as specified by
96x1H-IPI.2.2.100
|
The file name of the Signed Application / Library Software Package installed in the telephone, see
96x1PKG.2.3.100 in [7.1-10] and 96x1H-IPI.3.1.100 flowchart 3c-1.
|
|
BACKUPAPP
(see Valid Values)
|
The name of the Backup Package stored in the telephone, with a maximum length as specified by
96x1H-IPI.2.2.100
|
The file name of the Backup Package that will be installed if the application files become corrupted, see
96x1H-IPI.3.1.100 flowchart 3c-1.
|
|
BOOT1INUSE
(see Valid Values)
|
The name of the boot1 file stored in the telephone, see 96x1PKG.2.3.300 in [7.1-10].
|
The name of the boot1 file stored in the telephone, see
96x1H-IPI.3.1.100 flowchart 3c-2.
|
|
BOOT2INUSE
(see Valid Values)
|
The name of the boot2 file stored in the telephone, see 96x1PKG.2.3.300 in [7.1-10].
|
The name of the boot2 file stored in the telephone, see
96x1H-IPI.3.1.100 flowchart 3c-2.
|
|
NVBRIGHTNESS
(“4”)
|
1 ASCII numeric digit,
“1” through “5”
|
Display backlight brightness, see 96x1LA.5.1.200 in [7.1-5].
|
|
NVCONTRAST
(“8”)
|
1 or 2 ASCII numeric digits,
“1” through “15”
|
Display contrast setting,
see 96x1H-IPI.3.1.100 and
96x1LA.5.1.200 in [7.1-5].
|
|
NVDEBUG
(“0”)
|
1 ASCII numeric digit,
“0” or “1”
|
Debug mode status, see
96x1LA.6.2.800 in [7.1-5].
|
|
NVLANGFILE
(“”)
(null string)
|
0 to 32 ASCII characters
as specified in
96x1H-IPI.2.2.100
|
The name of the language file to use during initialization,
see 96x1H-IPI.3.1.100.
|
|
NVLANGNAME
(“English”)
|
1 to 24 Unicode characters
|
Used to find another language file that supports the same language that was supported by the file named by NVLANGFILE if the file named by NVLANGFILE file is replaced or deleted (see flowchart 4 of 96x1H-IPI.3.1.100).
|
|
NVLOGSTAT
(“0”)
|
1 ASCII numeric digit,
“0” through “8”
|
Manually-entered syslog status, see 96x1H-IPI.5.1.1300.
|
Approved
|
NVBM1BRIGHTNESS
(“4”)
|
1 ASCII numeric digit,
“1” through “5”
|
Display backlight brightness for the
first attached button module, see 96x1LA.5.1.200 in [7.1-5].
|
|
NVBM2BRIGHTNESS
(“4”)
|
1 ASCII numeric digit,
“1” through “5”
|
Display backlight brightness for the second attached button module, see 96x1LA.5.1.200 in [7.1-5].
|
|
NVBM3BRIGHTNESS
(“4”)
|
1 ASCII numeric digit,
“1” through “5”
|
Display backlight brightness for the
third attached button module, see 96x1LA.5.1.200 in [7.1-5].
|
|
NVSSON
(“242”)
|
3 ASCII numeric digits,
“128” through “254”
|
Manually-entered Site-Specific Option Number for DHCP,
see 96x1H-IPI.5.1.604,
96x1LA.6.2.1700H in [7.1-5].
|
Rationale:
|
The default value for NVSSON was changed from 176 (the default value used by the 46xx IP telephones) to 242 because IETF RFC 3942 reclassified option numbers 128-223 to be publicly-defined options, not site-specific options. However, NVSSON will still be allowed to use the reclassified option numbers because some customers (perhaps with older DHCP servers) may wish to continue using them.
|
Approved
|
NVTRUSTLIST
(“”)
(null string)
|
0 to 255 ASCII characters:
zero or more file names or URLs, separated by commas without any intervening spaces
|
The list of files that were downloaded containing trusted certificates,
see 96x1H-IPI.3.1.100,
flowcharts 3a-3 and 3b-3.
|
