In this example, in the event of a connection loss with the registered MGC, the G250/G350
searches for the primary MGC on its MGC list for 20 minutes. If the G250/G350 does not
establish a connection with the primary MGC within this time, it searches for the other MGCs on
the list for a total of 40 minutes.
Use the show recovery command to display the reset times.
Accessing the registered MGC
Access the MGC according to the following:
If the MGC is an S8300 Server, enter session mgc
●
If the MGC is an S8400, S8500, or S8700-series server, use the set mediaserver
●
command to manually define the MGC's IP address, and then enter session mgc to
access the MGC
If the G250/G350 includes a local S8300, enter session icc to access the S8300. You can
use this command whether or not the local S8300 is the G250/G350's registered MGC.
Note:
Both the session mgc command and the session icc command open a
Note:
telnet connection to the MGC.
To open a connection directly to the Avaya Communication Manager System Access Terminal
(SAT) application in the MGC, add sat to the command. For example:
G350-001
To open a connection to the MGC's LINUX operating system, do not add sat to the command.
For example:
G350-001
Monitoring the ICC or LSP
When a local MGC controls telephone services on the Avaya G250/G350 Media Gateway in
ICC or LSP mode, the G250/G350 monitors the connection with the MGC. If the connection with
the MGC is lost, the G250/G350 starts a recovery process.
Use the set icc-monitoring command to control heartbeat monitoring of an ICC or
●
LSP. The enable parameter enables heartbeat monitoring. The disable parameter
disables heartbeat monitoring.
Use the show icc-monitoring command to display the status of the ICC/LSP
●
monitoring process.
(super)# session mgc sat
(super)# session mgc
Configuring the Media Gateway Controller (MGC)
Issue 5 June 2008
97