Note:
|
If the telephone does DHCP after a power-up or a reset, it always does so first on either the default VLAN administered in the network (if L2Q = “2”, or if L2Q = “0” or “1” and NVL2QVLAN = “0”) or on the VLAN indicated by NVL2QVLAN (if NVL2QVLAN is greater than zero and if L2Q is equal to “0” or L2Q is equal to “1”). If it is desired to use DHCP to change the VLAN on which the telephone operates, the DHCP server on the initial VLAN must deliver the desired value of L2QVLAN. The telephone will then do a reset and invoke DHCP on the desired VLAN.
|
Note:
|
All configuration files (see 96x1PKG.2.4.100 in [7.1-10]) will be downloaded from a single server using a single protocol (i.e., HTTPS or HTTP). However, even if HTTPS is used to download configuration (and language) files, the telephone will also try to download language files via HTTP (if HTTPSRVR is not null, see the bottom of flowchart 3a-2), because language files provided in the software distribution package will probably be stored with the configuration files, but there may not be a mechanism for a customer to get customized language files onto an Avaya server for use with HTTPS.
|
Note:
|
HTTP file download during telephone initialization does not support use of HTTP Basic or Digest access authentication or proxy servers.
|
Note:
|
Apache HTTP servers return a 503 (Service Unavailable) response code if the number of connections exceeds its MaxClients parameter, and does not refuse additional TCP connections until the number of “pending” connections exceeds its ListenBackLog parameter. Unknown as to whether Apache returns the Retry-After header or whether it allows setting the retry interval.
|
Note:
|
A non-zero value of GIPADD is not required because a system on a LAN without a router could be a valid configuration. Likewise, on a LAN without a router, NETMASK would be all zeroes. Since the test of whether two IP addresses are on the same subnet is whether the result of a logical AND of each against the subnet mask is the same, an all-zeroes subnet mask would result in any value of GIPADD as being on the same subnet as any value of IPADD. However, if there is no router and L2Q = “0” (auto), tagging will not be turned on.
|
Note:
|
An H.323 signaling message can be used to cause an active, registered telephone to perform a reset to force the download of a new version of software.
|
Rationale:
|
If an IP address was obtained via DHCP, it is important to release it before a reset because, otherwise, many IP addresses on a default VLAN could be made unusable for a period of time (until the leases expired). One of the possible reasons for using a separate VLAN for voice endpoints is when not enough IP addresses are available on the default VLAN, so failure to release the IP addresses when switching VLANs would defeat this purpose and probably prevent some phones from receiving an initial DHCPOFFER message.
|
96x1H-IPI.3.1.110: Validation of Signed Software Packages |
Approved
|
All downloaded Signed Software Packages will be validated as follows.
If a Signing Authority Certificate File named “IPTSAcert.txt” is not contained in the package, or if the Signing Authority Certificate included in the Signing Authority Certificate File is not properly signed by the Avaya Product Root Certificate Authority Certificate, the downloaded package is not valid. The Signing Authority Certificate File may contain a chain of up to 8 certificates. The signature of each certificate will be validated against the next certificate in the chain, and the last certificate in the chain must be signed by the Avaya Product Root Certificate Authority certificate
If the digital signature contained in a Signature File is not correct, the downloaded package is not valid.
|
Note:
|
Signature verification is specified in 96x1H-IPI.5.1.1550.
|
Note:
|
96x1PKG.2.3.300 in [7.1-10] specifies that a copy of the Avaya Product Root Certificate Authority Certificate is included in every Application Software Package to authenticate the Signing Authority Certificate of subsequently downloaded Signed Software Packages.
|
Approved
|
If the Signed Software Package is too large, it is not valid, and endptAPPstat (see MIB Group 3 in 96x1H-IPI.5.1.1100) will be set to 2 if the package is a Signed Application/Library Software Package and endptRFSstat will be set to 2 if the package is a Signed Kernel/Root File System Software Package.
If the file type is not correct as specified by 96x1PKG.2.3.100 in [7.1-10], the downloaded package is not valid, and endptAPPstat will be set to 3 if the package is a Signed Application/Library Software Package and endptRFSstat will be set to 3 if the package is a Signed Kernel/Root File System Software Package.
If a Hardware Version File (see 96x1PKG.2.3.400 in [7.1-10]) and a corresponding Signature File are not contained in the package, or if the digital signature contained in the corresponding Signature File is not valid for the Hardware Version File, the downloaded package is not valid, and endptAPPstat will be set to 4 if the package is a Signed Application/Library Software Package and endptRFSstat will be set to 4 if the package is a Signed Kernel/Root File System Software Package.
If none of the Hardware Version Identifiers contained in the Hardware Version File (see 96x1PKG.2.3.400 in [7.1-10]) are valid for the telephone, the downloaded package is not valid, and endptAPPstat will be set to 5 if the package is a Signed Application/Library Software Package and endptRFSstat will be set to 5 if the package is a Signed Kernel/Root File System Software Package.
If two Software Packages of the correct type, as specified by 96x1PKG.2.3.250 in [7.1-10], and corresponding Signature Files are not contained in the package, or if the digital signature contained in either of the Signature Files is not valid for the corresponding Software Package, the downloaded package is not valid, and endptAPPstat will be set to 4 if the package is a Signed Application/Library Software Package and endptRFSstat will be set to 4 if the package is a Signed Kernel/Root File System Software Package.
If a downloaded file is not valid, it will not be stored in non-volatile memory.
When a Software Package is installed in non-volatile memory, a checksum will also be stored in non-volatile memory.
|
Note:
|
Signature Files and the Signing Authority Certificate are not required to be saved in non-volatile memory after the signed files are validated.
|
96x1H-IPI.3.1.115: Compatibility of Software Packages |
Approved
|
A “source” software package will be checked for compatibility with other (“target”) software packages by comparing strings in the “source” package’s Hardware Version File (see 96x1PKG.2.3.400 in [7.1-10]) with the names of “target” software packages that are either already installed, downloaded pending installation, or due to be subsequently downloaded.
For each line in the Hardware Version File except the first line, if there is a “target” software package with the same
and portions, and an [] portion that is greater than or equal to that of at least one of the strings on that line of Hardware Version File, then the “source” software package is compatible with that “target”. If any of the lines in the Hardware Version File do not meet this criteria, the “source” software package is not compatible with the “target” software package.
|
Note:
|
Since each Signed Software Package contains two Software Packages, each “source” software package (which is always a Signed Software Package, even if it has already been installed) will be checked for compatibility with zero, one or two “target” software packages, depending on the number of lines of compatibility strings in the Hardware Version File. A Signed Application/Library Software Package may be checked against a Kernel Software Package and/or a Root File System Software Package, and a Signed Kernel/Root Software Package may be checked against an Application Software Package and/or a Library Software Package.
Package numbering sequences are specified in 96x1PKG.2.3.250 in [7.1-10].
|
Approved
|
If a “source” software package is to be checked for compatibility with a Signed Software Package that has not yet been downloaded, two strings will be created for comparison with the strings in the Hardware Version File, based on the name of the “target” Signed Software Package that has not yet been downloaded, by combining the
and portions of the “target” Signed Software Package name with the corresponding [] portions of the “target” Signed Software Package name.
|
Example:
|
If a Signed Application/Library Software Package is to be checked for compatibility with a Kernel Software Package and a Root File System Software Package in a Signed Kernel/Root Software Package named “S96x1_UKR_V2r5_V1.tar” that has not yet been downloaded, the strings “UK_V2r5” and “UR_V1” would be created for comparison purposes.
|
| |
Note:
|
This requirement is referenced in flowcharts 3a-1b and 3b-1b of 96x1H-IPI.3.1.100 because these exceptions were previously included there. They were moved here to ensure that the same exceptions are applied in both places.
|
Approved
|
If the value of NVIPADD is not null, or if the value of L2QVLAN was set via LLDP, L2QVLAN will not be set from a value in a configuration file.
|
Rationale:
|
The above requirement gives manual programming and LLDP a higher precedence for setting L2QVLAN than a configuration file.
|
Approved
|
If the value of L2Q was set via LLDP, L2Q will not be set from a value in a configuration file.
If the value of PHY2VLAN was set via LLDP, PHY2VLAN will not be set from a value in a configuration file.
|
Rationale:
|
The above requirements give LLDP a higher precedence for setting L2Q and PHY2VLAN than a configuration file.
|
Approved
|
If the value of SIG was set via the SIG Craft Local procedure (see 96x1LA.6.2.1600H in [7.1-5]), SIG will not be set from a value in a configuration file.
|
Rationale:
|
The above requirement gives manual programming a higher precedence for setting SIG than a configuration file.
|
Approved
for R6.2.1+
|
If the value of HEADSYS was not set in a configuration file, and if the value of CALLCTRSTAT was set to “1”, the value of HEADSYS will be set to “1”.
|
Rationale:
|
The above requirement results in providing a different default value for HEADSYS for call center operation than for normal operation.
|
Note:
|
Indications as to whether the values of persistent parameters (L2Q, L2QVLAN and SIG) were set via a specific mechanism must also be maintained in non-volatile memory, and should be reset to “no” when the parameter is initialized to its default value by the CLEAR or the Reset Values procedures.
|
96x1H-IPI.3.1.150: Power-up / reset interval |
Approved
|
DHCP DISCOVER procedures will begin within 30 seconds after a power-up or reset if a manually-entered IP address is not used.
|
Note:
|
For 96x0 R3.1, this interval is 35 seconds on a 9640 and 45 seconds on a 9670.
|
Rationale:
|
This requirement has been around since the early 46xx telephones, and was intended to specify an upper limit on the time taken by startup procedures that are under the control of the telephone (once DHCP and file downloading begin, performance is also affected by the performance of the servers and the network).
|
96x1H-IPI.3.1.200: Loss of Ethernet after initialization |
Approved
|
An interrupt screen will be displayed as specified by 96x1COPS.7.2.100 of [7.1-4] and below, with the priority specified for No Ethernet screens by 96x1COPS.7.2.200 in [7.1-4], at any time after the completion of the procedures specified in 96x1H-IPI.3.1.100, if it is detected that the link has failed on the Ethernet line interface for more than approximately 1 second.
No text will be displayed on the
|
R6.0
|
Title Line or on the Prompt Line.
|
R6.1+
|
Status Line.
|
Approved
|
The following will be displayed, centered in the application area:
No Ethernet.
Waiting…
No softkeys will be labeled.
The screen will remain on the display until the link is re-established, at which time the screen will be restored to its previous state.
|
Note:
|
When the Ethernet line interface link fails, the 802.1X Supplicant, if enabled, should enter the Disconnected state, as specified in the Supplicant PAE state machine in [7.2-7a]
(see also 96x1H-IPI.5.1.240).
|
Rationale:
|
The interrupt screen specified above is not used until after file downloading is complete because it would not look good to over-write the logo image with this screen, and then restore the logo image when network connectivity is restored. In addition, Software Development had originally indicated that the WindML code used on the VxWorks platform to render graphical displays would not be loaded until after file downloading is complete, to keep as much RAM as possible available for downloading files, but this may no longer be true with Qt on Linux.
|
96x1H-IPI.3.1.300: Access Code Entry procedure |
Approved
|
When the Access Code Entry procedure is invoked, startup procedures will be terminated and the following will be displayed on the reserved text lines:
|
|
|
Enter code:|
#=OK
|
|
|
where “|” is the cursor. Each dial pad button press will be interpreted as the next digit of an access code. The numeric-only password text entry requirements of 96x1H-IPI.3.2.100 apply. All other button presses will be ignored. If the “#” button on the dial pad is pressed, operation will proceed as specified below.
|
|
|
Rationale:
|
This procedure provides more security than is provided by the 46xx telephones, which automatically invoke the MuteADDR# procedure if * is pressed while “* to program” is being displayed.
|
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: |
