Survivability And Migration Options - Avaya G250 Administration

Survivability and migration options

Several options exist to minimize network disruption in the event that connectivity between the
G250/G350 and the MGC is lost.
MGC list. You must register the G250/G350 with at least one, and up to four, MGCs. The
●
first MGC on the list is the primary MGC. If the G250/G350 cannot connect with, or loses
its connection with, the primary MGC, it attempts to connect with the other MGCs on the
list. See Configuring the MGC list
Standard Local Survivability (SLS). SLS consists of a module built into the G250 to provide
●
partial backup MGC functionality in the event that the connection with the primary MGC is
lost. This feature allows a local G250 to provide a degree of MGC functionality when no
link is available to an external MGC. It is configured on a system-wide basis using the
Provisioning and Installation Manager (PIM) (see
Alternatively, it can be configured on an individual G250 using the CLI. For more
information and instructions on configuring SLS, see
Local Survivability (SLS) on the G250
Note:
SLS survivability is not supported on the G350 or the G250-BRI.
Note:
Enhanced Local Survivability (ELS). ELS is available for both the G250 and the G350
●
using a local S8300 functioning in LSP mode. If the ECC stops serving the G250/G350,
the S8300 takes over the service.
Auto fallback to primary MGC. This feature provides a means by which a G250/G350
●
being serviced by its LSP can return to its primary MGC automatically when the
connection is restored between the G250/G350 and the MSG. By migrating the G250/
G350 to the MGC automatically, a fragmented network can be made whole more quickly,
without the need for human intervention. Auto fallback is configured via the Avaya
Communication Manager. For details, see the Administrator's Guide for Avaya
Communication Manager, 555-233-506.
Note:
Auto fallback does not include survivability. Therefore, there is a short period
Note:
during registration with the MGC during which calls are dropped and service is
not available. This problem can be minimized using the connection preservation
feature described below.
Connection preservation. This feature enables the G250/G350 to preserve the bearer
●
paths of stable calls in the event that the G250/G350 migrates to another MGC (including
an LSP), including migration back from an LSP to the primary MGC. A call for which the
talk path between parties in the call has been established is considered stable. A call
consisting of a user listening to announcements or music is not considered stable and is
not preserved. Any change of state in the call prevents the call from being preserved. For
example, putting a call on hold during MGC migration will cause the call to be dropped.
Special features, such as conference and transfer, are not available on preserved calls.
Configuring the Media Gateway Controller (MGC)
on page 62.
Accessing PIM
Chapter 5: Configuring Standard
on page 77.
on page 41).
Issue 1.1 June 2005 61