Filter
Top Products
RLC
2003 Avaya Inc. All Rights Reserved.
Page 8 of 12
Local Survivable Processor S8300.doc
registered to CLAN1 when there is a network outage between the G700 Gateway and the
primary gatekeeper, the G700 will attempt to re-register with CLAN1, then continue
down the list trying to register with CLAN 2, then the LSP.
If the Avaya G700 Gateway is able to reach the LSP, the MGP will reset and
begin the search at the top of the list once again, attempting one registration with each
address in the list.
If the Avaya G700 Gateway is unable to reach the LSP, the G700 Gateway will
start its search at the top of the list. If the G700 continues in this fashion and is unable to
reach a gatekeeper for duration of the total search time, the MGP will reset and start at
the top of the list.
8. Transition to the LSP
8.1 Avaya G700 Gateway
The transition to the LSP is an automatic process. When an endpoint determines
that it can no longer communicate with the primary gatekeeper, it searches its list of
gatekeeper candidates until it finds one that responds to the registration request and
allows the endpoint to register.
The Avaya G700 Gateway will determine that it does not have connectivity with
the primary gatekeeper and then search for the next available gatekeeper. Once contact
can be made with a new gatekeeper, the MGP reboots in order to synchronize the call
states on the G700 Gateway with the call states on the new gatekeeper. Any calls that are
up at the time of the failure will remain up until the G700 finds a new gatekeeper and
resets the call states. When the G700 is in this state, no features can be used, nor can new
calls be made until the G700 is re-registered with a gatekeeper.
The amount of time an Avaya G700 Gateway takes to transition over to the LSP
varies based on where the failure happened, the transition point and primary search time,
and where LSPs are administered in the G700 Gateway gatekeeper list.
Avaya G700 Gateways send a keep alive message once every 24 seconds. If the
failure occurs in the network, and the G700 Gateway does not receive a response to three
keep-alive messages in a row, it will then enter into recovery mode and begin the search
for a new gatekeeper. This takes a maximum of 72 seconds. If the failure occurs at the
CLAN or the primary gatekeeper, the communication link is closed and the G700 is
alerted to this closure immediately.
The next stage of a failover is the search time to find a new gatekeeper. The
Avaya G700 Gateway will try to re-register with the same IP address first. If that address
is unreachable, the Avaya G700 Gateway will continue through the list until it is able to
register with one of the addresses. The best-case scenario is approximately 11 seconds.