Survivability Configuration Examples - Avaya 9601 Administering

With SES and non-AST controllers, contact data is cached until the maximum cache size of 25
contacts is reached; configuration data is cached without limitations. With SM, the PPMs are in sync
and the data is sent to the PPM; data is cached only in case of failure.
Moving subscriptions to a secondary SM/BSM for simultaneous registration has the following effects
on call states and transitions:
• Transition from one SM to another SM/BSM is comprised of:
- Limbo - The phone has lost its connection to its primary controller, but has not yet detected
this regardless of whether a user is on a call or not.
- Moving Subscriptions Interval (MSI) - The phone has detected a lost connection to the
primary controller and since it has already registered with a non-primary controller, this is the
brief interval between limbo and successful subscription to the non-primary controller. The
subscription can be moved regardless of whether a user is on a call or not.
- Call Preservation - During an active call, the phone has detected a lost connection to the
primary controller and exhibits media preservation behavior.
• The Call Preservation Message Box or the Acquiring Services screen are not displayed during
the Moving Subscription Interval (MSI).
MSI transition and failback to the primary SM occurs according to the failback behavior described in
3. Select the active controller
Related Links

Survivability configuration examples

Surviveability hardware/software requirements
Survivability configuration examples
Several survivability configurations are available, depending on your controller and system
management environment, as shown in the illustrations that follow.
Related Links
Supporting survivability
Configuration Example 1
Configuration Example 2
Configuration Example 3
Configuration Example 1
SIP software Release 6.0 and later offers simultaneous registration with multiple controllers, and
improved feature availability during and after failover to a secondary controller.
August 2015 Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP Deskphones SIP
on page 128.
on page 123
on page 122
on page 123
on page 124
on page 124
Comments on this document? infodev@avaya.com
on page 125
Supporting survivability
123