The following parameters will be initialized to the specified default value and will be settable only to the ASCII equivalent of a value received in the specified location(s) in a DHCP message. They will not be settable via a SET command in a configuration file, and they will not be testable via an IF command in a configuration file.
The path name that is prepended to all file names used in HTTPS GET operations during startup,
see 96x1H-IPI.3.1.100.
TLSPORT
(“411”)
DHCPv4 ACK
NVSSON option
DHCPv6
Reply
VSI option 242
2 to 5 ASCII numeric digits,
“80” through “65535”
TCP port number used for HTTPS file downloading,
see 96x1H-IPI.3.1.100 and 96x1H-IPI.5.1.500.
Rationale:
Since port 443 (the "well known" port for TLS and SSL) was used for secure web admin on CM, port 411 was used for secure file downloads to IP telephones to avoid contention.
96x1H-IPI.2.1.800: Parameters (with persistent initialization parameters) that can be set via DHCP or config file
Approved
The following parameters will be initialized from the corresponding persistent parameter at startup and after a reset. The parameter will subsequently be set to the ASCII equivalent of a value received in the specified location(s) in a DHCP message. Subsequent to that, it will also be settable via a SET command in a configuration file. It will not be testable via an IF command in a configuration file.
DHCPv4 ACK
siaddr field (non-zero value only) and/or the NVSSON option
DHCPv6
Reply
VSI option 242
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
HTTP server IP addresses, see 96x1H-IPI.3.1.100.
Rationale:
HTTPSRVR is settable via a SET command in a configuration file because it may be used to specify a different server from which to obtain software code files than was used to obtain the configuration files. For example, if the configuration files are obtained via HTTPS, TLSSRVR must be set via DHCP, but if it is then desired to obtain the software code file from an HTTP server with a different IP address (e.g., if the HTTPS server is a CM, but the customer doesn’t want to burden the CM file server with providing the much larger code files), the customer may want to set HTTPSRVR in the configuration file (although it could also be set via DHCP).
In VPN mode, a file server IP address cannot be obtained from the “outer” DHCP server, usually cannot be obtained from a security gateway, and cannot be obtained from an “inner” DHCP server (via a unicast DHCPINFORM request) unless the security gateway provides an IP address for the “inner” DHCP server, so NVHTTPSRVR is provided so that a file server IP address can be preconfigured and saved in non-volatile memory.
Approved
MCIPADD
NVMCIPADD
(see
96x1H-IPI.2.1.1150)
DHCPv4 ACK
NVSSON option
DHCPv6
Reply
VSI option 242
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].
