Avaya Media Gateway G350, Maintenance Manual

Page: 68 / 332

Avaya Communication Manager controlled maintenance
System resets
68 Maintenance of the Avaya G350 Media Gateway
June 2004
Network Fragmentation
A likely outcome to an H.248 link recovery scenario is that a network of media gateways and IP
endpoints, initially registered to the primary server, may now be registered to a number of different LSPs
in the network. This can be very disruptive in that network capability may be highly compromised.
Resources at various points in the network may be available in only limited quantities, or not at all.
The SAT commands
list media-gateway
and
status media-gateway
can show those network elements
that are not registered with the primary server. If the technician is on site, the illumination of the
YELLOW ACT LED on the LSP is an indication that something has registered with that LSP, and
therefore, that the network is fragmented. At the present time, two methods are available to recover from
a fragmented network:
•
Use the S8300 Web Interface to shut down each LSP
•
Execute
reset system 4
on each LSP
•
Shut down Communication Manager on every LSP
Use the S8300 Web Interface
You can use the S8300 Web Interface to shutdown and reboot each LSP registered with the server. This is
the recommended way for customers to reestablish the LSP’s connection to the primary server.
Voice mail adjuncts
(INTUITY, INTUITY Audix) During Link Recovery, callers connected to AUDIX
remain connected even if they hang up. Such calls might
be automatically disconnected by AUDIX if the
connection remains intact without the calling party
entering tone commands to AUDIX or voicing a message.
Call Detail Recording (CDR) Call records cannot reflect the correct disconnect time if
the calling party hangs up before the link recovers.
Call Management System (CMS) Measurements collected during the recovery period might
be inaccurate in those reports that rely upon time-related
data.
Property Management System (PMS) Automatic Wake-up, Daily Wake-up, and Housekeeping
Status features might not operate as expected if the link
fails and the time to search for alternate resources exceeds
the PMS application’s time-out parameters.
For example, if a guest has a wake-up call schedule for
6:15 AM and the H.248 link goes down at 6:10 but
recovers at 6:20, then the guest receives no wake up call at
6:15.
Conversant voice response systems Conversant applications that utilize timing loops, time-
related methods, or events might not perform as intended.
In addition, applications that do not accommodate time-
outs or missing state transition(s) might behave
unpredictably.
Table 27: H.248 Link Recovery feature/adjunct interactions 2 of 2
Feature or adjunct Description
2 of 2