User's Manual

The B5800 Branch Gateway supports Session Manager 6.1 and Session Manager 6.0.
Depending on the Session Manager version you are using, see one of the following sections:
Session Manager 6.1 configuration required for survivable extension support on
page 185
Session Manager 6.0 configuration required for survivable extension support on
page 188
Survivable extension configuration checklist
Use this checklist to monitor your progress as you administer survivable extensions.
# Description Section
1 Add a user on Session Manager
for each survivable extension.
Depending on the version of Session
Manager you are using, see one of the
following:
Session Manager 6.1 configuration required
for survivable extension support on
page 185.
Session Manager 6.0 configuration required
for survivable extension support on
page 188.
2 Enable SIP extension support on
the branch.
See Enabling branch SIP extension
support on page 192.
3 Add SIP extensions and users to
the branch.
See Adding SIP extensions and users to the
B5800 Branch Gateway on page 194.
Survivability operation
During normal operation, survivable extensions register with the Communication Manager
Feature Server at headquarters. However, they can also be configured to automatically failover
to their local B5800 Branch Gateway system for survivable telephony services when the
connection to the Avaya Aura
®
Session Manager is lost for any reason.
Each survivable extension phone monitors its own connectivity to the Avaya Aura
®
Session
Manager (and secondary Avaya Aura
®
Session Manager if configured). If it detects loss of
connectivity, it automatically registers with the B5800 Branch Gateway and switches to
survivability operation. There will be a short unavailability of services while failing over.
The survivable phones in the branch will typically be able to make and receive calls processed
by the B5800 Branch Gateway approximately 2 minutes after a WAN failure. When the phone
Extension administration
182 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com