Avaya S8300 DJ Equipment User Manual


 
RLC
2003 Avaya Inc. All Rights Reserved.
Page 11 of 12
Local Survivable Processor S8300.doc
12. Transition Back to the Primary Call Controller
The return of service to the primary call controller requires manual intervention.
The LSP must undergo a reset system 4, which will close all communication links with
the LSP, forcing all endpoints to reregister with the primary call controller. This time to
transition is again dependent upon the ordering and administration of alternate controller
lists, but the initial discovery that the connection has been broken is immediate. Both IP
endpoints and G700 Gateways will discover right away that the link is no longer usable
and begin the search for another controller.
Since the return to the primary call controller is not call preserving, it is
recommended that this outage be planned and only done when service will be the least
affected.
13. Upgrades and License Files
The same Avaya MultiVantage Software version must be running on the LSPs
that is running on the primary call controller in order to help ensure that the system
translations will work on the LSP after the translations are transferred to the LSP. This
requirement is enforced through the transfer mechanism, which will not run between a
primary call controller and an LSP that do not have the same Avaya MultiVantage
Software. LSPs should be upgraded first, and Avaya Call Processing Software on the
LSPs should be left out of service while the software upgrade is being completed on the
primary call controller. The LSP Avaya MultiVantage Software upgrade is a manual
process and requires that each LSP be upgraded individually.
The license file turns on the LSP feature bit and activates the LSP. The license
file for the Avaya S8300 Gateway, as a survivable processor or as a standalone, keys off
of the serial number of the hosting Avaya G700 Gateway. Therefore, each LSP requires
its own license file to be loaded. This license must match or exceed the primary call
controller’s in capacity limits in order to allow the primary controller’s translations to
load on the LSP without exceeding the limits set by the license file.
14. Conclusion:
Traditionally, duplication of data has been done by a call processor, which
protects against server difficulties and provides this protection invisibly. When
increasing the distances between headquarters and remote branch offices however, it
becomes more likely that a network outage causes a loss of communications. Setting up
Local Survivable Processors on corporate networks provides coverage with full feature
functionality in the event of a network outage. With the Avaya MultiVantage Software
based solutions, the system administrator is empowered to select which strategy for
recovery is priority: reconnecting the location to the network for interoffice
communications, or reestablishing local call traffic. Avaya’s S8300 Media Server can be
established as an LSP in a network controlled by an Avaya S8700 Media Server.