User Experience During Stable Failover - Avaya 9601 Administering

During MSI the Contacts button remains activated and the user can view the Contacts Screen.
Contacts can be changed during failover transition up to the maximum cache size regardless of
which primary controller is used. The New, Edit, or Delete softkeys display during failover. During
MSI transition, the +AddtoContact function on a web page will fail and the Prompt Line will display
"Contact cannot be saved." Selecting a contact or pressing the Call softkey produces an error beep
and the Prompt Line displays "Limited phone service."
All screens are visible. Any changes made under the Avaya menu Options & Settings take place on
all screens (including the Home Screen) immediately. All changes other than Contacts are cached
and are updated to the PPM with which the phone successfully registers.
All Audio Receive, Transmit, Top Line, Web Push, or phoneXML pushes operate normally.
For incoming calls during MSI, the phone stops alerting and disconnects the call. If the phone is
alerting when the phone's secondary server goes down (no MSI), the phone will keep on ringing. An
incoming call will be ended when the link between the Session Manager that routed the call and the
phone has gone down. For example, if the deskphone has a primary SM (SM1) and a secondary
SM (SM2), and receives a call directly from the secondary SM but SM2 goes down, the call that was
received from SM2 is terminated.
Media preservation only keeps shuffled calls or calls using direct media between endpoints up with
a direct RTP stream until the call has ended. The user can only put this call on Hold, resume the
call, or end the call. The user can also answer any incoming call and the media preserved call will
be put on hold.
Related Links
User experience during failover transition

User experience during stable failover

• A Failover "warning" icon displays on the top line. The Failover icon is shown whenever the
primary call server is not active. The Failover icon provides a continuous reminder indicating
the deskphone has detected that the primary server is unavailable and that features will be
limited until the primary server returns.
• Multiple Call Appearances are consistent with Normal Operation.
• If a call originates using the secondary server, Hold, Conference and Transfer are supported.
• AST features (FNUs and Bridged call appearances) are unavailable when failing over to a
secondary gateway.
• Unsupported features and related softkeys are not displayed.
• The dial plan does not remain as it was in normal operation. The dial plan in failover is set with
the DIALPLAN parameter which should contain all needed strings while failed over. Calls
between sets in the branch are supported, using their usual extensions.
• Outgoing Calls that would normally route to the SES or SM/Avaya Aura
Manager will instead be routed to the local gateway.
August 2015 Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP Deskphones SIP
on page 135
Comments on this document? infodev@avaya.com
About the user interface/failover experience
®
Communication
137