Limitations After A Successful Failover - Avaya J100 Series Installing

Limitations after a successful failover

Failover to a Session Manager
instance
After a phone successfully fails over to a secondary Session Manager, all features and
functionality work properly for new calls. However, there are limitations to modify a preserved call.
Failover to a Branch Session Manager
After a phone successfully fails over to Branch Session Manager, the value of the parameter
FAILBACK_POLICY changes to Admin. In this case, you must go to the System Manager and
manually re-register the phone with Session Manager.
Note:
Administration of Session Manager and Branch Session Manager nodes are explicitly required
in the System Manager user record.
Failover to a proxy other than Avaya Aura
The limitations after a phone fails over to a proxy other than Avaya Aura
• A conference is limited to three parties and is hosted by the phone.
• Contacts can be used and new contacts can be saved on the phone. New contacts are
cached on the phone, and after failback to Avaya Aura
with Avaya Aura
• The dial plan for Avaya Aura
46xxsettings.txt file is used.
• The following Avaya Aura
- Last party drop
- Send All Calls (Do Not Disturb)
- Presence
- Calling party block/unblock
- Call park/unpark
- All forms of call pickup
- Priority calls
- MLPP functionality
- Auto callback
- Malicious call trace
- EC500 on/off
- Transfer to voicemail
- Paging
- Call recording
December 2018
®
.
®
is unavailable. Instead, the dial plan configured in the
®
features are unavailable:
Installing and Administering Avaya J100 Series IP Phones
Comments on this document? infodev@avaya.com
Limitations after a successful failover
®
®
, the new contacts are synchronized
®
are:
181