Avaya one-X 9611G Installing And Maintaining Download

Page: 33 / 90

Power-Up and Reset Operation (Dynamic Addressing Process)

Issue 5

August 2014

user that the phone is active and has not "locked up," and to provide useful information about
the status of network, server or downloading operations before the availability of dial tone.

Initialization

The following process describes the software architecture as well as providing a high-level
overview of how the deskphone is expected to operate during startup and software upgrades.
This is by no means a comprehensive description of all of the internal tasks performed during
startup.

Files are stored in five areas of reprogrammable non-volatile (flash) memory in the deskphones:

●

A boot program area

●

Two Kernel/Root File Systems

●

One Application File System

●

One Temporary Storage area

Two Kernel/Root File Systems are supported in case one becomes corrupted, but only one is
activated when the deskphone 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 deskphone starts up, the boot programs check the kernel or the root file system to
ensure that the files are not corrupted. If the file system is not corrupted, the programs transfer
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 deskphone 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