96x1H-IPI.2.1.1000: Parameters (with persistent initialization parameters) that can be set only via config file |
Approved
|
The following parameters will be initialized from the corresponding persistent parameters at startup and after a reset, 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.
|
|
Parameter
Name
|
Persistent Parameter Name
and
(default value)
|
Valid Values
|
Notes
(usage and references)
|
|
AGCHAND
|
NVAGCHAND
(“1”)
|
1 ASCII numeric digit,
“0” or “1”
|
Handset AGC status, see 96x1COPS.6.1.300 in [7.1-4], 96x1LA.5.1.200, 96x1LA.5.3.2500, and 9xxxLA.6.2.300 in [7.1-5].
|
|
AGCHEAD
|
NVAGCHEAD
(“1”)
|
1 ASCII numeric digit,
“0” or “1”
|
Headset AGC status, see 96x1COPS.6.1.300 in [7.1-4], 96x1LA.5.1.200, 96x1LA.5.3.2500, and 9xxxLA.6.2.300 in [7.1-5].
|
|
AGCSPKR
|
NVAGCSPKR
(“1”)
|
1 ASCII numeric digit,
“0” or “1”
|
Speaker AGC status, see 96x1COPS.6.1.300 in [7.1-4], 96x1LA.5.1.200, 96x1LA.5.3.2500, and 9xxxLA.6.2.300 in [7.1-5].
|
|
AUTH
|
NVAUTH
(“0”)
|
1 ASCII numeric digit,
“0” or “1”
|
Authentication flag for configuration files,
see 96x1H-IPI.3.1.100
(flowchart 3a-1a).
|
Note:
|
If NVAUTH is set to “1”, the phone will only accept a configuration file downloaded over a secure (TLS) connection, and will not download a new code file unless the configuration file was downloaded over such a secure connection.
|
96x1H-IPI.2.1.1100: Persistent parameters that can be set via DHCP or config file |
Approved
|
The following persistent parameters will be initialized to the specified default values at manufacture and will be settable via a DHCP message (in a DHCPv4 ACK NVSSON option, or in a DHCPv6 Reply VSI option 242) or via a SET command in a configuration file, but will not be testable via an IF command in a configuration file.
|
|
Persistent Parameter Name and
(default value)
|
Valid Values
|
Notes
(usage and references)
|
|
DOT1X
(“0”)
|
1 ASCII numeric digit,
“0”, “1” or “2”
|
Specifies 802.1X pass-through operation,
see 96x1H-IPI.5.1.240.
|
Approved
for R6.2.1+
|
DOT1XEAPS
(“MD5”)
|
3 ASCII characters,
“MD5” or “TLS”
|
Specifies the EAP method used by 802.1X,
see 96x1H-IPI.5.1.240.
|
Approved
|
DOT1XSTAT
(“0”)
|
1 ASCII numeric digit,
“0”, “1” or “2”
|
Specifies 802.1X Supplicant operation,
see 96x1H-IPI.5.1.240.
|
Approved
for R6.3+
|
DOT1XWAIT
(“0”)
|
1 ASCII numeric digit,
“0” or “1”
|
Specifies whether the telephone will wait for 802.1X to complete before initiating DHCP, see 96x1H-IPI.3.1.100 flowchart 1.
|
Approved
|
ICMPDU
(“1”)
|
1 ASCII numeric digit,
“0”, “1” or “2”
|
Specifies whether ICMP Destination Unreachable messages are generated,
see 96x1H-IPI.5.1.304.
|
|
ICMPRED
(“0”)
|
1 ASCII numeric digit,
“0” or “1”
|
Specifies whether ICMPv4 Redirect messages will be processed,
see 96x1H-IPI.5.1.304.
|
|
L2Q
(“0”)
|
1 ASCII numeric digit,
“0”, “1” or “2”
|
802.1Q tagging auto/on/off,
see 96x1H-IPI.5.1.220,
and 96x1LA.6.2.100 in [7.1-5].
|
|
LOGLOCAL
(“7”)
|
1 ASCII numeric digit,
“0” through “8”
|
Local logging control, see endptResetLog, endptRecentLog and endptStartupLog in Group 3 of the MIB in 96x1H-IPI.5.1.1100.
|
|
NDREDV6
(“0”)
|
1 ASCII numeric digit,
“0” or “1”
|
Specifies whether IPv6 Neighbor Discovery Redirect messages will be processed,
see 96x1H-IPI.5.1.306.
|
|
NVVPNMODE
(“0”)
|
1 ASCII numeric digit,
“0” or “1”
|
Specifies whether VPN is supported, see flowcharts 1, 3a-1a, 3b-1a, 3f, 4 and 4d in 96x1H-IPI.3.1.100,
and 96x1H-IPI.5.1.600.
|
Note:
|
In 96xx R3.1 and R3.1.1, NVVPNMODE is not settable via DHCP.
|
Approved
|
PHY1STAT
(“1”)
|
1 ASCII numeric digit,
“1” through “6”
|
Ethernet line interface status,
see 96x1H-IPI.5.1.100,
and 96x1LA.6.2.1000H in [7.1-5].
|
|
PHY2STAT
(“1”)
|
1 ASCII numeric digit,
“0” through “6”
|
Secondary Ethernet interface status,
see 96x1H-IPI.5.1.100,
and 96x1LA.6.2.1000H in [7.1-5].
|
Rationale:
|
PHY1STAT and PHY2STAT are persistent because the Ethernet switch IC must be reset if the PHY1 or PHY2 mode is changed. Such a reset will cause link integrity to be interrupted, which will cause an Ethernet-powered endpoint to be power cycled, which would cause any new mode saved only in volatile memory to be lost.
|
Approved
|
PROCPSWD
(“27238”)
|
Prior to R6.2.4:
0 to 7 ASCII numeric digits,
null (“”) and
“0” through “9999999”
|
Specifies the local (dial pad) procedure access code, see
96x1H-IPI.3.1.300, and
96x1LA.6.1.300 in [7.1-5].
|
Approved
for R6.2.4+
|
|
R6.2.4+:
4 to 7 ASCII numeric digits,
“0000” through “9999999”
|
|
Note:
|
If the value of PROCPSWD has less than 4 digits when R6.2.4+ is installed, the value will be changed back to the default value.
|
Note:
|
27238 corresponds to CRAFT on the dial pad.
|
Note:
|
PROCPSWD may also be set via H.323 procedures, see Step 16d of 96x1Tel.2.1.400 and Step 17 of 96x1Tel.2.1.500 in [7.1-6], and requirements 122598-12 and 122598-13 in COMPAS ID 122598.
|
Approved
|
PROCSTAT
(“0”)
|
1 ASCII numeric digit,
“0” or “1”
|
Local (dial pad) procedure status, see 96x1H-IPI.3.1.100 and
96x1H-IPI.5.1.600 (flowchart DHCP 1).
|
Note:
|
The default value of PROCSTAT corresponds to full access to local dial pad procedures.
Since PROCSTAT is persistent, if it is desired to re-enable full access to local dial pad procedures on a phone on which they have been disabled, the phone must be restarted on a network where PROCSTAT is explicitly set to “0”.
|
Rationale:
|
PROCSTAT was added as a more secure alternative than PROCPSWD, with the disadvantage that the dial pad procedures for changing values would not be available to authorized personnel either.
|
Approved
|
REUSETIME
(“60”)
|
1 to 3 ASCII numeric digits,
“0” and “20” through “999”
|
Number of seconds to wait for successful completion of DHCP before reusing previous parameters on the default (port) VLAN, see 96x1H-IPI.5.1.600 (flowchart DHCP 2b).
|
Rationale:
|
Setting very short reuse intervals does not give DHCP servers a reasonable time to respond and could cause undesirable interactions.
|
Approved
|
SIG
(“0”)
|
1 ASCII numeric digit,
“0”, “1” or “2”
|
Signaling protocol download flag, see 96x1H-IPI.3.1.100 flowcharts 3a-1 and 3b-1, and 96x1LA.6.2.1600 in [7.1-5].
|
|
SNMPADD
(“”)
(null string)
|
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
|
Allowable IP source address(es) for SNMP queries, see 96x1H-IPI.5.1.1100.
|
|
SNMPSTRING
(“”)
(null string)
|
0 to 32 ASCII characters
|
SNMP community name string,
see 96x1H-IPI.5.1.1100.
|
Note:
|
SNMPADD and SNMPSTRING may also be set via H.323 procedures, see Step 16d of 96x1Tel.2.1.400 and Step 17 of 96x1Tel.2.1.500 in [7.1-6], and requirements 122598-10 and 122598-11 in COMPAS ID 122598.
|
Approved
|
TLSSRVRID
(“1”)
|
1 ASCII numeric digit,
“0” or “1”
|
Specifies whether the identity of a TLS server is checked against its certificate,
see 96x1H-IPI.5.1.1550.
|
Rationale:
|
TLSSRVRID is saved in nonvolatile memory for VPN configurations in which certificates are used for authentication, but for which an IP address of a DHCP server on the corporate intranet is not provided from which to obtain the Site-Specific Option.
|
Approved
|
VLANTEST
(“60”)
|
1 to 3 ASCII numeric digits,
“0” through “999”
|
Number of seconds to wait for a DHCPOFFER on a non-zero VLAN, see 96x1H-IPI.5.1.600 (flowchart DHCP 2).
|
Rationale:
|
VLANTEST ensures that the phone will be able to return to the default VLAN if an invalid VLAN ID value is given to the phone, or if a phone is moved to a port where the value in NVL2QVLAN is not valid. A relatively long interval (60 seconds) was chosen as the default value because a mass restart after a power interruption may be a more common fault condition. A flood of DHCPDISCOVER messages could prevent the DHCP server from responding for quite a while. A router resetting could also significantly delay DHCPOFFER messages relayed from another subnet.
|
Approved
for R6.1+
|
VUMCIPADD
(“”)
(null string)
|
0 to 255 ASCII characters:
zero or more IP addresses in dotted decimal
or DNS name format,
separated by commas without any intervening spaces
|
Specifies IP addresses for Visiting User call servers,
see 96x1Tel.2.1.300 in [7.1-6].
|
Directory: public -> downloadFile.jsp?file= -> resources -> sites -> AVAYA -> content -> live -> SOLUTIONSpublic -> The german unification, 1815-1870public -> Preparation of Papers for ieee transactions on medical imagingpublic -> Harmonised compatibility and sharing conditions for video pmse in the 7 9 ghz frequency band, taking into account radar usepublic -> Adjih, C., Georgiadis, L., Jacquet, P., & Szpankowski, W. (2006). Multicast tree structure and the power lawpublic -> Duarte, G. Pujolle: fits: a flexible Virtual Network Testbed Architecturepublic -> Swiss Federal Institute of Technology (eth) Zurich Computer Engineering and Networks Laboratorypublic -> Tr-41. 4-03-05-024 Telecommunicationspublic -> Chris Young sets 2016 “I’m Comin’ Over” Tour headlining datesSOLUTIONS -> CM: How to enable 'auto answer' feature
Share with your friends: |
