About The User Interface/Failover Experience - Avaya 9601 Administering

System Failover and Survivability
• If users are part of a corporate Directory or database, access may be limited to local contacts
only.
• If the phone is logged out during failover, the local phone cache is cleared and the phone may
become inoperable until it can be reset on the original controller after failback.
• With SIP software Release 6.0 and later, the phone will accept calls from any of the proxies it is
registered with when the phone is simultaneously registered to multiple controllers. There is no
visual indication to the user differentiating calls from different feature servers. In the case of
Multiple Feature Servers, one feature server can know about one call on the phone and
another feature server or controller can know about another call on another call appearance.
The second Feature Server does not have any information about the first call displayed on the
phone and there will be limitation in the features that can be applied to the first call. When there
are multiple controllers, one controller may know about one call on the phone and another
controller can know about another call offered to the phone. If both controllers are connected to
the same feature server e.g., Communication Manager, Communication Manager "knows"
about both calls and the user can resume a held call, conference call, or call transfer normally.
If both controllers are not connected to the same feature server, the second Feature Server
would not have any information about the first call displayed on the phone. In this scenario
features that can be applied to the first call would be limited because all the call data is stored
in Communication Manager; SM does not store any information related to any call.
• Preserved Media Connections - Applies only to Session Manager configurations when moving
a subscription from one SM to another. As of SIP software Release 2.6 in a scenario where the
the primary SM fails, any active shuffled or direct media call will be preserved if a new call is
received while a preserved call is active. The phone allows the user to manually put the active
(media preserved) call on hold or allows the user to switch to the new call and automatically put
the preserved call on hold using auto-hold. A media preserved call displays the failover icon in
place of a call-associated icon that is left justified on an application line preceding the displayed
name or phone number. When active on a media preserved call the softkeys displayed are
"Hold, blank, blank, End Call." Conference and Transfer are not available. When a media
preserved call is put on hold, the softkeys displayed are "Resume, blank, blank, blank, blank."
The phone can receive incoming calls at this point but is not available to make outgoing calls or
to invoke AST features. The phone supports media preservation sufficient for alternate
registration; if a phone experiences a mid-dialog failure (for example, a timed out or failed SIP
request, or a socket-level failure), the phone behaves as if the dialog had been terminated (but
does not send a BYE) and preserves the media session until the near-end user hangs up.
Related Links
Failover/failback behavior

About the user interface/failover experience

The user interface experiences described below expand upon the information provided in
failback behavior on page 131. User guides for each deskphone model also provide this information
in a "user-friendly" format.
Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP Deskphones SIP
134
on page 131
Comments on this document? infodev@avaya.com
Failover/
August 2015