User Experience During Failback - Avaya 9601 Administering

System Failover and Survivability
• Emergency calls (to the provisioned emergency numbers as defined in the dial plan) will be
permitted whether those phones are in failover or normal mode. The Emergency softkey is
available when a new controller is found.
• The MWI (Message Waiting Indicator) will be cleared, but voice mail is still available.
• One-button voice mail access will be available if the central voice mail system continues to
operate and will make a PSTN call to the voice mail system. Depends on correct provisioning.
• Local deskphone features will be available: audio selection (speaker / headset / handset),
mute.
• Local phone applications will be available: local call redial, Call Logs, Volume Control, local
contacts, speed-dials, auto-dials, WML browser (WML Browser is dependent on network
access to the WML server) but cannot be changed.
• Nothing is saved in PPM when failing over to a secondary (for example, Audiocodes) gateway.
• Basic local features if provisioned (call forwarding) will be available: call hold, consultative hold,
Attended Transfer, Unattended Transfer, call forward all, call forward on busy, call forward on
no answer, three party conferencing of calls originated in Failover Operation (including drop
last party). Additional in-call features will be available if supported by the local proxy - find me,
inbound call management and outbound call management.
• Contact or Autodial Favorite Features are displayed on the Phone Screen.
• Presence is not supported.
• "A" (Avaya) Menu and Home Screen Options & Settings are blocked under minimal
survivability configurations. Any of the more extensive survivability configurations (for example,
moving subscriptions to a secondary SM/BSM for simultaneous registration) allow access to
the Avaya Menu and updates to Options & Settings. Likewise, Contacts can be accessed and
updated.
• CRAFT changes may be made and are saved locally on the phone.
• If the phone is logged out during failover, the local phone cache is cleared.
Related Links
About the user interface/failover experience

User experience during failback

Failback (F/B) transition occurs when the Phone detects that the primary server is up, regardless if
secondary controller is up.
• Failback will not happen during an active call. If no calls are in progress, failback occurs and
the user interface returns to its normal appearance.
• While switching from one server to another (including while waiting for an active call to end)
reject any new inbound calls (including emergency callbacks) or outbound call requests.
• AST features return.
• Pre-failover Visiting User status maintained after failback.
Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP Deskphones SIP
138
on page 134
Comments on this document? infodev@avaya.com
August 2015