Avaya 9608 Administration page 163

Be in a pushable state during transition, when the primary controller is lost and the
●
deskphone is not connected to a secondary controller. Once the deskphone is registered
on secondary controller and regardless if the deskphone is active on a call, the deskphone
is in a pushable state, just as if were connected to primary server. The deskphone is
always in a pushable for state for all normal or barge-in Top Line. Display, Audio Receive/
Transmit, or phonexml pushes for all transition conditions.
In general, the deskphone does not attempt to preserve SIP transactions in progress when a
controller failure is detected, and some mid-call features like conferencing can fail. However, in
some scenarios the same transaction may succeed if re-attempted once the transition to a new
controller has been completed.
The deskphone always registers to a configured controller with the credentials (username/
password) of the user who is currently logged-in, even if the deskphone transitions from one
controller to another.
As described in the corresponding deskphone user guide, certain features may not be available
and functionality may be limited or work differently during any stage of failover, "limbo,"
transition, or failback. Calls can still be placed and received, and other deskphone functions
remain active. The following apply when a deskphone is in failover mode:
If the user is active on a call, a failover icon displays when failing over to a non-AST
●
controller and messages like "Link recovery." "Limited phone service." and "Calls may be
lost." inform the user of a failover situation. The message "Limited phone service" also
displays during failover transition from one Session Manager server to another when the
subscriptions have not yet been moved successfully to the secondary Session Manager.
The only user options are to navigate to the Phone screen by pressing the OK softkey or
the Phone button or hang up the call.
When failing over to a third party secondary controller, the deskphone displays an
●
"Acquiring Services" screen. The deskphone might also display a Call Preservation
message window. Most other screens and applications except for Craft screens are
unavailable until the deskphone finds an active controller. However, the user can navigate
to the Contacts, Call Forward feature, Avaya (A) Menu or Call Log applications (if
administered). The user can go to the Home screen by pressing the Phone button.
If a call is active when failover occurs, that call will remain active. The user cannot initiate
●
new calls while the deskphone transitions to the alternate server.
During failover to secondary controller for alternate registration, the user can access
●
Contacts, the Call Forward button, Call Log, standard Avaya menu or Home Screen
applications if administered. The user cannot make calls in these applications.
Certain softkeys do not display and their related functions are unavailable.
●
Call appearance information does not display while dialing, but does appear when Call is
●
pressed.
Call connection may take longer than usual.
●
Upon failover, any active conference calls, call transfers, and held calls will be dropped.
●
Controller Determination and Survivability Activity
Issue 3 January 2014 159