Avaya 9608 Administration page 164

System failover and survivability
Emergency calls may or may not work, depending on the stage of failover and the
●
functionality available on the alternate server.
Bridged call appearances are not available. Despite a "Log Bridged Calls" option setting of
●
yes, bridged calls are not logged during failover.
During the transition stage, incoming calls may not be received, and may get diverted to
●
voice mail.
Call forwarding may not be available unless the extension to which calls are being
●
forwarded is on the same server as the forwarding extension.
The Message Waiting Indicator is cleared, but voice mail may still be available, if the voice
●
mail server to which calls are being sent is not in failover.
Advanced features like Call Park/Unpark, Priority Call, or Automatic Callback are not
●
available. Most features on the Feature menu will not be available. Favorite features are
not available during failover.
Once the transition to a new server has occurred, changes to Avaya (A) Menu options can
●
be made/saved during failover. Note that any new or changed settings for these options
will become effective when the deskphone fails back to its original server.
If the deskphone operates under the latest software, Contacts can be accessed and
●
changed during and after failover to the alternate server.
If the deskphone operates under the latest software, the end user can access Home
●
Screen Web links/pages during failover, however, any "click to dial" links will not work until
the deskphone transitions to the alternate server.
If users are part of a corporate Directory or database, access may be limited to local
●
contacts only.
If the deskphone is logged out during failover, the local deskphone cache is cleared and
●
the deskphone may become inoperable until it can be reset on the original controller after
failback.
The deskphone accepts calls from any of the proxies it is registered with when the
●
deskphone is simultaneously registered to multiple controllers. There is no visual
indication to the user, which indicates that the calls are originating from different feature
servers. In the case of Multiple Feature Servers, one feature server can know about one
call on the deskphone and another feature server or controller can know about another call
on another call appearance. The second Feature Server does not have any information
about the first call displayed on the deskphone and there will be limitation in the features
that can be applied to the first call. When there are multiple controllers, one controller may
know about one call on the deskphone and another controller can know about another call
offered to the deskphone. If both controllers are connected to the same feature server. For
example, Communication Manager. Communication Manager "knows" about both calls
and the user can resume a held call, conference call, or call transfer normally. If both
controllers are not connected to the same feature server, the second Feature Server would
not have any information about the first call displayed on the deskphone. In this scenario
features that can be applied to the first call would be limited because all the call data is
160 Administering Avaya 9601/9608/9608G/9611G/9621G/9641G IP Deskphones SIP
Comments? infodev@avaya.com