User Interface In Failover/Failback; User Experience During Failover Transition - Avaya 9601 Administering

Related Links

User interface in failover/failback

User experience during failover transition

User experience during stable failover
User experience during failback
User interface failover operation for features
User interface in failover/failback
• Failover (F/O) transition - Connection to SES/SM failed, the phone detects F/O and blocks new
invites while the phone is in transition.
• Stable in F/O where the non-primary proxy is the active controller.
• Fail Back (F/B) transition to normal - The phone detects that the primary server is up,
regardless if the secondary is up. New invites are blocked while the phone is in transition. The
phone is in a stable Normal mode with SES/SM as the active controller. Any cached changes
(for example, to Contacts or other Avaya Menu options and settings) are updated to the PPM
once the phone is registered back to the primary controller.
Related Links
About the user interface/failover experience
User experience during failover transition
SIP software Release 6.0 expanded deskphone reliability during the transition from one controller to
another.
Related Links
About the user interface/failover experience
Failover to a secondary controller for alternate registration (SES F/O to SM to a non-AST
controller) on page 135
Moving subscriptions from one SM to another SM/BSM (Branch System Manager) due to failover
page 136
Failover to a secondary controller for alternate registration (SES F/O to SM
to a non-AST controller)
Transition is comprised of the following conditions:
• Limbo - The phone has lost its connection to its primary controller, but has not yet detected this
condition regardless of whether a user is on a call or not.
• Acquiring Services - The phone has detected a lost connection to the primary controller and
displays an Acquiring Services Screen if the phone is idle.
• Call Preservation - During an active call, the phone has detected a lost connection to the
primary controller and displays a Call Preservation screen.
August 2015 Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP Deskphones SIP
on page 135
on page 135
on page 137
on page 138
on page 139
on page 134
on page 134
Comments on this document? infodev@avaya.com
About the user interface/failover experience
on
135