Mgc Management - Avaya G250 Overview

Summary of services
You can configure Standard Local Survivability (SLS) to enable a local Branch Gateway to
●
provide a degree of MGC functionality when no link is available to an external MGC. SLS
is configured on a system-wide basis using the Provisioning and Installation Manager
(PIM). Alternatively, SLS can be configured from the individual Branch Gateway itself
using the CLI. SLS is supported as follows in the various models of the G250:
G250-Analog. Supported for all analog interfaces.
●
G250-BRI. Supported for all analog interfaces.
●
G250-DCP. Supported for all analog and DCP interfaces.
●
G250-DS1. Supported for all analog interfaces.
●
You can configure Enhanced Local Survivability (ELS) by installing an S8300 in the Branch
●
Gateway as a Local Survivable Processor (LSP). In this configuration, the S8300 takes
over to provide continuous telephone service if all external media servers become
unavailable. Calls in progress continue without interruption when the S8300 takes over.
You can configure the dialer interface to connect to the Branch Gateway's primary MGC
●
via a serial modem in the event that the connection between the Branch Gateway and the
MGC is lost.
You can configure the Avaya CM to support the auto fallback feature, which enables a
●
Branch Gateway being serviced by an LSP to return to its primary MGC automatically
when the connection is restored between the Branch Gateway and the MGC. When the
Branch Gateway is being served by its LSP, it automatically attempts to register with its
MGC at periodic intervals. The MGC can deny registration in cases in which it is
overwhelmed with call processing, or in other configurable circumstances. By migrating
the Branch Gateway to the MGC automatically, a fragmented network can be unified more
quickly, without the need for human intervention.
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 preserving
migration feature.
The Branch Gateway features a dynamic trap manager, which enables you to ensure that
●
the Branch Gateway sends traps directly to the currently active MGC. If the MGC fails, the
dynamic trap manager ensures that traps are sent to the backup MGC.

MGC management

The MGC is managed by the Avaya Communication Manager (CM). The Branch Gateway
supports Avaya Communication Manager (CM) release 3.1 and is backwards compatible with
release 2.0.
42 Overview for the Avaya G250 and Avaya G350 Media Gateways