Avaya one-X 9601 Installation And Maintenance Manual page 19

Hide thumbs Also See for one-X 9601:
Table of Contents

Advertisement

one Application File System, and
one Temporary Storage area.
Two Kernel/Root File Systems are supported in case one becomes corrupted, but only one is
activated when the telephone powers up or resets. Temporary Storage is used to store a new
Signed Application/Library Software Package that has been downloaded by the current
application until it can be installed by a process in the active Kernel/Root File System after the
next reset.
When a telephone starts up, the boot programs check the Kernel/Root File System that has
previously been marked as the one to be activated to ensure that it has not become corrupted,
and if it has not, it transfers control to a process in that file system. If that file system is
corrupted, the boot program checks the other Kernel/Root File System. If that file system is not
corrupted, it is marked as the one to be activated, the value of RFSINUSE is set to the name of
the Signed Kernel/Root Software Package that was used to install that file system, and control
is transferred to a process in it. If both Kernel/Root File Systems are corrupted, the telephone
will not operate and must be returned for repair.
A process in the active Kernel/Root File System first checks whether a Signed Application/
Library Software Package is stored in Temporary Storage, and if it finds one, it installs the
Application Software Package and/or the Library Software Package if either has a different file
name than the currently installed version, replacing the existing corresponding files in the
Application File System. The copy of the Signed Application/Library Software Package stored in
Temporary Storage is then deleted. If a Signed Application/Library Software Package is not
found in Temporary Storage, the process checks the integrity of the application files, and if they
are corrupted, the process installs files from the Backup Package, replacing the corrupted
application files in the Application File System. Any time an Application Software Package or a
Library Software Package is installed, the value of the persistent parameter APPINUSE is set to
the file name of the Signed Application/Library Software Package from which it was installed. If
the application files are not corrupted, or after the Backup Package has been installed, control is
transferred to the application installed in the Application File System. Note that the processes in
the Kernel/Root File System do not connect to the network or download files.
The application then connects to the network, obtains any necessary IP address information,
and download files, starting with the upgrade and settings configuration files, and including
Signed Software Packages and other separately downloaded files such as Language Files and
Certificate Files. When a Signed Software Package (which can contain either Kernel and Root
Software Packages or Application and Library Software Packages) is downloaded, it is initially
stored in volatile memory (RAM). Other downloaded files (such as Language Files and
Certificate Files) are installed directly in the Application File System.
When either type of Signed Software Package is downloaded, the Signing Authority Certificate
is extracted from the package and is validated using a copy of the Avaya Product Root
Certificate Authority Certificate that is contained in the existing application software files. If the
Signing Authority Certificate is invalid, the package is deleted. If the Signing Authority Certificate
is valid, the Hardware Version File in the package is validated using the corresponding
Signature File in the package and the Signing Authority Certificate. If the signature is invalid, the
package is deleted. If the signature is valid, the Hardware Version File is used to validate
whether the package is valid for the model and hardware version of the telephone. If it is invalid,
Power-Up and Reset Operation (Dynamic Addressing Process)
Issue 1 December 2010
19

Advertisement

Table of Contents
loading

Table of Contents