Names of all types of parameters, and all valid values of parameters that may be tested via an IF command in a configuration file (see 96x1PKG.2.4.100 in [7.1-10]), will only use ASCII characters.
Rationale:
Parameter names will only use ASCII characters so that they can be recognized in a case-insensitive manner, as specified in 96x1H-IPI.5.1.604 and by 96x1PKG.2.4.100 in [7.1-10], and testable values will only use ASCII characters so that case-insensitive comparisons can be done as specified by 96x1PKG.2.4.100 in [7.1-10], without the need for the phone to know upper- and lower-case equivalents for all non-ASCII characters. Parameter names are only shown using all upper-case characters in this document so that they stand out.
Approved
Parameter names will never be longer than 30 characters.
Parameter values will never be longer than 255 characters.
Rationale:
Software development requested the above limits so that they could use fixed-sized buffers and data structures.
Approved
After initialization, some values may be changed via DHCP (see 96x1H-IPI.5.1.600), via a SET command in a configuration file (see 96x1PKG.2.4.100 in [7.1-10]), via LLDP (see 96x1H-IPI.5.1.260), via H.323 signaling or procedures, or internally via software. Values will not be changed unless the new value meets any specified validity requirements (e.g., number and/or type of characters, etc.) for that value. Attempts to assign values to parameters that are not explicitly specified in this document or in other applicable requirements / feature specification documents will be ignored.
For IPv4 address values, a value of “0.0.0.0” and a value of “” (null) will be treated as equivalent.
For IPv6 address values, a value of “::” and a value of “” (null) will be treated as equivalent.
Parameters will be stored in volatile memory and will be initialized after power-up or a reset (see 96x1H-IPI.3.1.100) to the value of the corresponding persistent parameter (if it has one) or (if it does not have one) to the specified default value.
Persistent parameters will be stored in non-volatile memory, and will be initialized to default values at manufacture. Downloading new software will not automatically reinitialize the persistent parameters. However, if a value stored in non-volatile memory is not valid for the current software due to being set by a different version of software, that value will be reinitialized to the default value for the current software.
Note:
Persistent parameters can be reset to their default values by the CLEAR craft procedure, see 96x1LA.6.2.600 in [7.1-5].
Approved
Semi-persistent parameters will be stored in volatile memory that does not get cleared or changed if the telephone resets and will be initialized only after power-up, not after a reset.
96x1H-IPI.2.1.100: Testable 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, but will be testable via an IF command in a configuration file.
Parameter Name
and
(default value)
Valid Values
Notes (usage and references)
GROUP
(“0”)
1 to 3 ASCII numeric digits,
“0” through “999”
Group identifier, see
96x1LA.6.2.900 in [7.1-5].
Note:
GROUP may also be set via H.323 procedures, see Step 16d of 96x1Tel.2.1.400and Step 17 of 96x1Tel.2.1.500 in [7.1-6], and requirement 122598-15 in COMPAS ID 122598.
Approved
MACADDR
(see Valid Values)
6 pairs of ASCII hexadecimal characters separated by colons: hh:hh:hh:hh:hh:hh
with hex characters A-F encoded as upper-case characters:
the MAC address of the telephone
See 9xxxHW.2.6.100 in [7.1-2].
Note:
Using MACADDR in an IF command allows customized settings to be provided for an individual phone.
Rationale:
Hexadecimal characters A-F used in MACADDR must use a single case because MACADDR can be used as a device identifier for 802.1X in DOT1XID (see 96x1H-IPI.5.1.240), which is case-sensitive. This issue was first identified when a phone changed from H.323 to SIP software, which then failed authentication because the new software did not use the same case as the previous software.
