Server initialization, recovery, and resets
Link Recovery
Maintenance Procedures
139
December 2003
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:
•
Execute reset system 4 on each LSP
•
Shut down Communication Manager on every LSP
Execute reset system 4
In order to force Media Gateways and IP endpoints to re-register with the primary server, execute a reset
system 4 command on each G700 containing an LSP, thus forcing any G700s and IP endpoints registered
to the LSP to search for and re-register with the primary server. The expectation is that these endpoints
will correctly perform the search and find the primary server; however, there is no guarantee that this will
be the result.
Shut down Communication Manager on every LSP
The only way to be certain that G700s and endpoints re-register with the primary server is to shut down
Communication Manager on every LSP in the network, using the Linux command stop -acfn. Afterward,
the primary server SAT commands list media-gateway or status media-gateway can verify whether all
the network endpoints re-registered with the primary server. The Linux command start -ac issued to each
LSP will then restart Communication Manager on each of those platforms.
H.323 gateway-to-endpoint Link Recovery
The H.323 link between an Avaya Media Gateway and an H.323-compliant IP endpoint provides the
signaling protocol for
•
Call setup
•
Call control (user actions such as Hold, Conference, or Transfer) while the call is in progress
•
Call tear-down
If the link goes down, Link Recovery preserves any existing calls and attempts to re-establish the original
link. If the endpoint cannot reconnect to the original Gateway, then H.323 Link Recovery automatically
attempts to connect with alternate TN799DP (C-LAN) circuit packs within the original server’s
configuration or to a Local Spare Processor (LSP).
H.323 Link Recovery does not diagnose or repair the network failure that caused the link outage,
however it:
•
Attempts to overcome any network or hardware failure by re-registering the IP Endpoint with its
original Gateway.
•
Maintains calls in progress during the re-registration attempt.
•
Continues trying to reconnect if the call ends and the IP Endpoint has not yet reconnected to its
original Gateway.
•
Attempts connecting to and registering with an alternate Gateway if so configured.
Table 51, Synopsis of recovery outcomes,
on page 140 provides a synopsis of the recovery outcomes.
Summary of Contents for CMC1
Page 1: ...Maintenance Procedures 555 245 103 Issue 1 1 December 2003 ...
Page 14: ...Contents 14 Maintenance Procedures December 2003 ...
Page 416: ...Additional maintenance procedures IP Telephones 416 Maintenance Procedures December 2003 ...
Page 426: ...Index X 426 Maintenance Procedures December 2003 ...