User Experience During Failback - Avaya 9608 Administrator's Manual

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.
●

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.
●
Users can access and update Avaya Menu/Home Screen options.
●
About the user interface/failover experience
Issue 1 May 2011 157