Avaya G250 Maintenance Manual page 80

Avaya Communication Manager controlled maintenance
Table 26: H.248 Link Recovery feature/adjunct interactions (continued)
Feature or adjunct
ESS
E911
Far-end mute
Hold
80 Maintenance for the Avaya G250 and Avaya G350 Media Gateways
Description
If the media gateway was connected to the
server through a CLAN, and the port network
the CLAN is on fails over to an ESS server, then
the IP phone attempts to register with the new
server, even if it is on a call. This is similar to a
scenario where the server goes through a
reboot and would not want the IP phone to
register. This is prevented by making the IP
phone send a flag in RRQ which is checked
against the user record to see if the user is on a
call. If the user record indicates there is no call,
the registration is denied.
During reconstruction, the server checks the IP
phone service state along with the check for
existence of a call associated with the user to
determine if it should deny registration or not. If
the IP phone indicates it does not have any call,
and the server thinks it is on a call, the call is
dropped, and the IP phone is allowed to register.
If a port network fails to an ESS server, the port
network calls are not reconstructed, whereas
the media gateway connections are
reconstructed. If there is a call between the port
network and media gateway, only the media
gateway part of the call is reconstructed.
An E911 call is treated just like any other call in
that it is preserved if possible (assuming the
bearer path stays up) during failover.
Individual participants in a conference call that
were muted by the far-end mute feature are still
muted during Connection Preservation.
However, these participants can no longer be
unmuted when the call is in a connection
preserved case.
Calls on hold are not preserved by Connection
Preservation. In addition, calls on hold are not
monitored to see if there is active VoIP traffic.
3 of 6