H. 323 Software ip interface Requirements / Feature Specifications compas id 143543 Issue 4 June 02, 2014 John W. Soltes (retired)



Download 4.77 Mb.
Page8/48
Date28.05.2018
Size4.77 Mb.
#51006
1   ...   4   5   6   7   8   9   10   11   ...   48



96x1H-IPI.2.1.900: Parameters that can be set via DHCP or config file


Approved

The following parameters will be initialized to the specified default value and will be settable to the ASCII equivalent of a value received in the specified location(s) in a DHCP message. Subsequent to that, they will also be settable via a SET command in a configuration file. They will not be testable via an IF command in a configuration file.




Parameter
Name


location in
DHCP
message

Valid Values

Notes
(usage and references)





DNSSRVR
(“”)
(null string)

DHCPv4 ACK
option #6

DHCPv6
Reply


VSI option 242

0 to 255 ASCII characters:
zero or more IP addresses in
dotted-decimal or colon-hex format,
separated by commas without any intervening spaces

DNS server IP address(es),
see
96x1H-IPI.5.1.750.

Note:

Development limits the maximum number of DNSSRVR IP addresses to be less than or equal to 30, whereas other parameters that can contain a list of IP addresses (such as HTTPSRVR and SNMPADD) have no such limits. This is not an issue for DNSSRVR because even if every address was an IPv4 address with the shortest possible length (a single digit per octet), only 32 would fit into 255 characters anyway.

Approved

DOMAIN
(“”)
(null string)

DHCPv4 ACK
option #15

DHCPv6
Reply


VSI option 242

0 to 255 ASCII characters

A string that is appended to DNS names in parameter values when they are resolved into IP addresses,
see
96x1H-IPI.5.1.750.

Note:

If the relevant servers are in more than one sub-domain, the DNS names for the servers should include the sub-domain name and DOMAIN should be set to the lowest-level common domain. For example, if the fully qualified domain name of the file server is AvayaFileServer.usae.Avaya.com and the fully qualified domain name of the syslog server is AvayaLogServer.global.avaya.com, HTTPSRVR should be set to “AvayaFileServer.usae”, LOGSRVR should be set to “AvayaLogServer.global”, and DOMAIN should be set to “avaya.com”. If DOMAIN is null, all DNS names must be fully qualified, unless the DNS server assumes a default domain for less-than-fully-qualified names.

Approved

HTTPDIR
(“”)
(null string)

DHCPv4 ACK
NVSSON option

DHCPv6
Reply


VSI option 242

0 to 127 ASCII characters

The path name that is prepended to all file names used in HTTP GET operations during startup,
see
96x1H-IPI.3.1.100.




HTTPPORT
(“80”)

DHCPv4 ACK
NVSSON option

DHCPv6
Reply


VSI option 242

2 to 5 ASCII numeric digits,
“80” through “65535”

TCP port number used for HTTP file downloading,
see
96x1H-IPI.3.1.100
and
96x1H-IPI.5.1.500.

Approved

REREGISTER
(“20”)

DHCPv4 ACK
NVSSON option

DHCPv6
Reply


VSI option 242

1 to 3 ASCII numeric digits,
“1” through “120”

The number of minutes the telephone waits before, and between, re-registration attempts, see Step 16c of 96x1Tel.2.1.400, and Step 16c of 96x1Tel.2.1.500 in [7.1-6].




UNNAMEDSTAT
(“1”)

DHCPv4 ACK
NVSSON option

DHCPv6
Reply


VSI option 242

1 ASCII numeric digit,
“0” or “1”

Specifies whether the telephone will attempt unnamed registration, see Step 4UR of 96x1Tel.2.1.300 in [7.1-6].




STATIC
(“0”)

DHCPv4 ACK
NVSSON option

DHCPv6
Reply


VSI option 242

1 ASCII numeric digit,
“0” through “3”

Contains bit flags to allow manually programmed values to override those received via DHCP or a configuration file, see 96x1H-IPI.3.1.100.

Note:

The lowest bit of STATIC is used to ensure the use of a manually programmed file server IP address, and the second lowest bit of STATIC is used to ensure the use of a manually programmed call server IP address, so values of “1” and “3” will ensure the use of a manually programmed file server IP address, and values of “2” and “3” will ensure the use of a manually programmed call server IP address. A value of “0” will maintain default operation where file server and call server IP addresses received via DHCP or via a configuration file are used instead of manually programmed values. If a manually programmed file server IP address is to be used, STATIC must be set via DHCP, because once a configuration file is received, it is too late to decide that a different IP address should have been used.

Directory: public -> downloadFile.jsp?file= -> resources -> sites -> AVAYA -> content -> live -> SOLUTIONS
public -> The german unification, 1815-1870
public ->  Preparation of Papers for ieee transactions on medical imaging
public -> Harmonised compatibility and sharing conditions for video pmse in the 7 9 ghz frequency band, taking into account radar use
public -> Adjih, C., Georgiadis, L., Jacquet, P., & Szpankowski, W. (2006). Multicast tree structure and the power law
public -> Duarte, G. Pujolle: fits: a flexible Virtual Network Testbed Architecture
public -> Swiss Federal Institute of Technology (eth) Zurich Computer Engineering and Networks Laboratory
public -> Tr-41. 4-03-05-024 Telecommunications
public -> Chris Young sets 2016 “I’m Comin’ Over” Tour headlining dates
SOLUTIONS -> CM: How to enable 'auto answer' feature

Download 4.77 Mb.

Share with your friends:
1   ...   4   5   6   7   8   9   10   11   ...   48




The database is protected by copyright ©ininet.org 2024
send message

    Main page