The following persistent parameters will be initialized to the specified default values at manufacture, and will be settable via a SET command in a configuration file, but will not be settable via a DHCP message, and will not be testable via an IF command in a configuration file.
Specifies whether unencrypted ISAKMP Notification Payloads will be accepted, see 96x1H-IPI.5.1.320.
Approved
for R6.2+
APPLICATIONWD
(“1”)
1 ASCII numeric digit,
“0” or “1”
Controls whether the application watchdog is enabled or disabled.
Note:
The application watchdog is a software process that monitors other software processes to determine whether they have become unresponsive, at which point it generates a log event and either kills the process or resets the telephone. No further requirements are specified for this operation. However, even though it may be preferable to stop a “non-critical” process, or even to reset the telephone to restore the operation of a critical process, the failure of such a process is still a bug that should be fixed.
Approved
AUDASYS
(“3”)
1 ASCII numeric digit,
“0”, “1”, “2” or “3”
Specifies the system setting for audible alerting, see
96x1COPS.6.1.100 in [7.1-4].
DHCPPREF
(“6”)
1 ASCII numeric digit,
“4” or “6”
Specifies whether new values received via DHCPv4 orDHCPv6 will be preferred when both are used, see
96x1H-IPI.5.1.600.
DHCPSRVR
(“”)
(null string)
0 to 255 ASCII characters:
zero or more IPv4 addresses
in dotted decimal
or DNS name format,
separated by commas without any intervening spaces
Specifies enterprise DHCP server IP address(es) from which configuration parameters may be requested through a VPN tunnel via a DHCPINFORM message, see 96x1H-IPI.4.2.200 and 96x1H-IPI.5.1.604.
DHCPSTAT
(“1”)
1 ASCII numeric digit,
“1”, “2” or “3”
Specifies whether DHCPv4, DHCPv6, or both will be used, see flowchart 1 in 96x1H-IPI.3.1.100 and
96x1H-IPI.5.1.300.
Rationale:
Even though “0” is not a valid value for DHCPSTAT to disable both DHCPv4 and DHCPv6, either DHCP client will be disabled if a corresponding IP address is manually programmed (see the Note in flowchart 1 in 96x1H-IPI.3.1.100). This is to ensure that both DHCP clients cannot be disabled if at least one IP address was not manually programmed, because if IPV6STAT (see below) is set to “0” (which would prevent even an IPv6 link-local address from being created), the telephone could be left with no network connectivity.
Approved
DROPCLEAR
(“1”)
1 ASCII numeric digit,
“0” or “1”
Specifies the treatment of received unencrypted (clear) IPsec packets, see 96x1H-IPI.5.1.310.
IPPREF
(“6”)
1 ASCII numeric digit,
“4” or “6”
Specifies which type of IP address will be tried first if DNS returns both types, see 96x1H-IPI.5.1.750.
IPV6STAT
(“0”)
1 ASCII numeric digit,
“0” or “1”
Specifies whether IPv6 will be supported, see flowchart 1 in 96x1H-IPI.3.1.100.
Rationale:
Requirement 1.2 in Section 5.3.5.4 of UCR 2008 [7.8-1d] requires that IPv6 be disabled until it is deliberately enabled.
Approved
LANG0STAT
(“1”)
1 ASCII numeric digit,
“0” or “1”
Specifies whether the built-in English language text strings are selectable by the user, see96x1LA.5.3.2600 in [7.1-5].
LANGxFILE,
where x is 1 through 4
(“”)
(null string)
0 to 32 ASCII characters:
zero or one file name
as specified in
96x1H-IPI.2.2.100
Specifies the name of language file x,
see flowchart 3a-2 and 3b-2 in
96x1H-IPI.3.1.100.
LANGLARGEFONT
(“”)
(null string)
0 to 32 ASCII characters:
zero or one file name
as specified in
96x1H-IPI.2.2.100
Specifies whether I-Use LED (red one) controlled by CM or locally by the phone, see 96x1Tel.3.2.2800, 96x1Tel.3.2.2650, 96x1Tel.3.2.2700, 96x1Tel.3.2.2800
Specifies the rate in seconds at which LLDP messages will be transmitted,
see 96x1H-IPI.5.1.260.
Rationale:
A msgTxInterval timer with a default value of 30 seconds is specified in Section 10.5.3.3 of IEEE 802.1AB-2005 [7.2-8a] and in Section 9.2.5.7 of IEEE 802.1AB-2009 [7.2-8b]. A range of 1 through 3600 for this timer is also specified in Section 9.2.5.7 of IEEE 802.1AB-2009 [7.2-8b].
Approved
for R6.3+
LOCALZIPTONEATT
(“35”)
2 ASCII numeric digit,
“0” through “95”
The Zip tone level can be attenuated according to the level specified in LOCALZIPTONEATT, (see Requirement 96x1Tel.3.2.3160).
Approved
for R6.2.3+
LOGTOFILE
(“0”)
1 ASCII numeric digit
“0” or “1”
Specifies whether optional debug printf strings will be logged to an internal file, see 96x1H-IPI.5.1.100;
also see 96x1LA.6.2.800 in [7.1-5].
Specifies the Certificate Authority Identifier to be used in a certificate request, see 96x1H-IPI.5.1.1600.
MYCERTCN
(“$SERIALNO”)
8 to 255 ASCII characters
that contain the string “$SERIALNO” or “$MACADDR”
Specifies the Common Name of the Subject of a certificate request,
see 96x1H-IPI.5.1.1600.
MYCERTDN
(“”)
(null string)
0 to 255 ASCII characters
Specifies additional information for the Subject of a certificate request,
see 96x1H-IPI.5.1.1600.
MYCERTKEYLEN
(“1024”)
4 ASCII numeric digits,
“1024” or “2048”
Specifies the bit length of the public and private keys generated for a certificate request, see 96x1H-IPI.5.1.1600.
MYCERTRENEW
(“90”)
1 or 2 ASCII numeric digits,
“1” through “99”
Specifies the percentage of a certificate’s Validity interval after which renewal procedures will be initiated,
see 96x1H-IPI.5.1.1600.
MYCERTURL
(“”)
(null string)
0 to 255 ASCII characters,
zero or one URL
Specifies the URL to be used to contact an SCEP server,
see 96x1H-IPI.5.1.1600.
MYCERTWAIT
(“1”)
1 ASCII numeric digit,
“0” or “1”
Specifies whether the telephone will wait until a pending certificate request is complete, or whether it will periodically check in the background,
see 96x1H-IPI.5.1.1600.
NORTELAUTH
(“1”)
1 ASCII numeric digit,
“1” through “4”
Specifies user authentication method for Nortel security gateways,
see 96x1H-IPI.5.1.320.
Approved
NVHTTPSRVR
(“”)
0 to 255 ASCII characters:
zero or more IP addresses in dotted decimal, colon-hex,
or DNS name format,
separated by commas without any intervening spaces
Enables IKE configuration mode,
see 96x1H-IPI.5.1.320.
NVIKEDHGRP
(“2”)
1 or 2 ASCII numeric digits,
“1”, “2”, “5”, “14” or “15”
Specifies the Diffie-Hellman Group to be used for establishing the IKE SA,
see 96x1H-IPI.5.1.320.
NVIKEID
(“VPNPHONE”)
0 to 30 ASCII characters
Specifies the identity to be used during IKE Phase 1 negotiation (also called the group name in XAUTH)
see 96x1H-IPI.5.1.320.
NVIKEIDTYPE
(“3”)
1 or 2 ASCII numeric digits,
“1”, “2”, “3”, “9” or “11”
Specifies the type of identification to use for establishing the IKE SA,
see 96x1H-IPI.5.1.320.
NVIKEOVERTCP
(“0”)
1 ASCII numeric digit,
“0”, “1” or “2”
Specifies whether and when to use TCP as a transport protocol for IKE, see the flowchart in 96x1H-IPI.4.2.200.
NVIKEP1AUTHALG
(“0”)
1 ASCII numeric digit,
“0”, “1” or “2”
Specifies the authentication algorithm to propose for use during IKE Phase 1 negotiation, see 96x1H-IPI.5.1.320.
NVIKEP1ENCALG
(“0”)
1 ASCII numeric digit,
“0” through “5”
Specifies the encryption algorithm to propose for use during IKE Phase 1 negotiation, see 96x1H-IPI.5.1.320.
NVIKEP1LIFESEC
(“432000”)
3 to 8 ASCII numeric digits
“600” through “15552000”
Specifies the proposed IKE SA lifetime in seconds, see 96x1H-IPI.5.1.320.
NVIKEP2AUTHALG
(“0”)
1 ASCII numeric digit,
“0”, “1” or “2”
Specifies the authentication algorithm to propose for use during IKE Phase 2 negotiation, see 96x1H-IPI.5.1.320.
NVIKEP2ENCALG
(“0”)
1 ASCII numeric digit,
“0” through “6”
Specifies the encryption algorithm to propose for use during IKE Phase 2 negotiation, see 96x1H-IPI.5.1.320.
NVIKEP2LIFESEC
(“432000”)
3 to 8 ASCII numeric digits,
“600” through “15552000”
Specifies the proposed IPsec SA lifetime in seconds, see 96x1H-IPI.5.1.320.
NVIKEPSK
(“”)
(null string)
0 to 30 ASCII characters
Specifies the pre-shared key to be used during IKE Phase 1 negotiation (also called the group password in XAUTH), see 96x1H-IPI.5.1.320.
NVIKEXCHGMODE
(“1”)
1 ASCII numeric digit,
“1” or “2”
Specifies the IKE Phase 1 negotiation mode, see 96x1H-IPI.5.1.320.
NVIPSECSUBNET
(“0.0.0.0/0”)
0 to 255 ASCII characters:
zero or more dotted decimal IPv4 address/integer strings,
separated by commas without any intervening spaces
Specifies IP address ranges that will use the VPN tunnel, see 96x1H-IPI.5.1.310.
Approved
NVMCIPADD
(“”)
0 to 255 ASCII characters:
zero or more IP addresses in dotted-decimal, colon-hex,
or DNS name format,
separated by commas without any intervening spaces
Call server IP addresses,
see 96x1Tel.2.1.300 in [7.1-6].
NVPFSDHGRP
(“0”)
1 or 2 ASCII numeric digits,
“0”, “1”, “2”, “5”, “14” or “15”
Specifies the Diffie-Hellman Group to be used for establishing the IPsec SA (also known as PFS), see 96x1H-IPI.5.1.320.
NVSGIP
(“”)
(null string)
0 to 255 ASCII characters:
zero or more IPv4 addresses in dotted decimal
or DNS name format,
separated by commas without any intervening spaces
VPN security gateway IP addresses,
see 96x1H-IPI.4.2.200.
NVTLSSRVR
(“”)
0 to 255 ASCII characters:
zero or more IP addresses in dotted decimal, colon-hex,
or DNS name format,
separated by commas without any intervening spaces
HTTPS file server IP addresses used to initialize TLSSRVR the next time the phone starts up, see 96x1H-IPI.2.1.600.
NVVPNAUTHTYPE
(“3”)
1 ASCII numeric digit,
“3” through “7”
Specifies the user authentication method, see 96x1H-IPI.5.1.320.
NVVPNCFGPROF
(“0”)
1 or 2 ASCII numeric digits,
“0”, “1”, “2”, “3”, “5”, “6”, “8”, “9” or “11”
VPN configuration profile,
see 96x1H-IPI.4.2.200.
NVVPNCOPYTOS
(“2”)
1 ASCII numeric digit,
“1” or “2”
Specifies whether to copy the TOS bits from the tunneled (inner) IP header to the tunnel (outer) IP header,
see 96x1H-IPI.5.1.310.
NVVPNENCAPS
(“0”)
1 ASCII numeric digit,
“0”,“1”, “2” or “4”
Specifies port numbers used for IKE and IPsec UDP encapsulation, and support for NAT traversal,
see 96x1H-IPI.5.1.310 and 96x1H-IPI.5.1.320.
NVVPNPSWD
(“”)
(null string)
0 to 30 ASCII characters
If the user password can be stored in NV memory (see NVVPNPSWDTYPE below), it is stored as the value of NVVPNPSWD, see 96x1H-IPI.4.2.210.
NVVPNPSWDTYPE
(“1”)
1 ASCII numeric digit,
“1” through “5”
Specifies whether and how the VPN user password will be stored,
see 96x1H-IPI.4.2.210.
NVVPNSVENDOR
(“4”)
1 ASCII numeric digit,
“1” through “5”
Specifies the IKE implementation to use, see the flowchart in 96x1H-IPI.4.2.200, and see 96x1H-IPI.5.1.320.
4 to 5 ASCII numeric digits
“6000” through “65535”
Specifies the UDP port used to receive discovery and test request messages from the SLA Monitor server, see 96x1H-IPI.5.1.400 and [7.1-31f].
SLMSRVR
(“0.0.0.0:0”)
7 to 21 ASCII characters:
one IP address in dotted-decimal format,
optionally followed by a colon and a port number
Specifies the source IP address and, optionally, the source port number of valid discovery messages from an SLA Monitor server, see 96x1H-IPI.5.1.930 and [7.1-31f].
SLMSTAT
(“0”)
1 ASCII numeric digit,
“0” or “1”
Specifies whether the SLA Monitor agent will be enabled, see 96x1H-IPI.5.1.930.
SLMTEST
(“50012”)
4 to 5 ASCII numeric digits
“6000” through “65535”
Specifies the UDP ports used for RTP and traceroute tests, see
96x1H-IPI.5.1.400 and [7.1-31f].
Avaya Diagnostics Server (ADS) R2.0 and below supports only 50012.
TRUSTCERTS
(“”)
(null string)
0 to 255 ASCII characters:
zero or more file names
(as specified in
96x1H-IPI.2.2.100)
or URLs, separated by commas without any intervening spaces
Specifies a list of files to be downloaded that contain certificates to be trusted,
see flowcharts 3a-3 and 3b-3
in96x1H-IPI.3.1.100.
VPNCODE
(“876”)
0 to 7 ASCII numeric digits,
null (“”) and
“0” through “9999999”
Specifies the VPN procedure access code, see 96x1H-IPI.3.1.300, and
96x1LA.6.1.300 and
96x1LA.6.2.2000 in [7.1-5].
Note:
876 corresponds to VPN on the dial pad.
Approved
VPNPROC
(“1”)
1 ASCII numeric digit,
“0”,“1” or “2”
Specifies whether VPNCODE can be used to access the VPN procedure at all, in view-only mode, or in view/modify mode, see 96x1H-IPI.3.1.300, and
96x1LA.6.1.300 and
96x1LA.6.2.2000 in [7.1-5].
Approved for 6.4+
WBCSTAT
(“1”)
1 ASCII numeric digit,
“0” or “1”
Specifies whether a wideband codec indication will be displayed when a wideband codec is being used. See 96x1COPS.2.1.100 in [7.1-4].
