
Branch Session Manager Administration
About Branch Session Manager
The Branch Session Manager provides a SIP-enabled branch survivability solution. It allows
a customer who has deployed SIP phones in a branch to receive LSP-style survivability. For
example, when the core Session Manager is unreachable, the SIP phones receive their
Communication Manager features from the LSP.
The Branch Session Manager supports phones which simultaneously register with both the
primary (and secondary, if configured) Session Managers in the core, and also with the Branch
Session Manager. The phones accept incoming calls from any of these servers. Thus there is
no outage to basic calling when a failure occurs and the phone is ready to receive a call from
any of its servers.
A typical branch setup contains the following components:
1. The Branch Session Manager provides service to users in case there is a WAN
failure between branch and core.
2. The Media Gateway provides among other functions the ability to connect branch
to PSTN and media services such as conferencing, tones, and announcements.
3. The LSP is a survivable processor for branch Media Gateway. The LSP starts to
work when the Media Gateway loses connectivity with Trunk Gateway, and register
itself to LSP.
4. End user devices (phones) register with the primary Session Manager as a primary
controller, but uses the Branch Session Manager as a third controller (in case of
WAN failure).
The Branch Session Manager provides service when the branch loses WAN connectivity. As
the result of WAN failure, there are two simultaneous processes triggered:
• The Branch Media Gateway loss of connectivity with the Trunk Gateway, and registers
itself to the Communication Manager LSP. As the result, the LSP starts to provide
service.
• The phones detect losing connectivity with core Session Manager and register the Branch
Session Manager as the new controller.
The Branch Session Manager has the same specifications as a Session Manager, and
provides local autonomy or survivability for SIP stations, trunks and applications. When
signaling is available to the core Session Manager, the branch SIP users can avail sequenced
applications. If the Branch Session Manager receives a request from (originating phase) or to
(terminating phase) any user then Branch Session Manager handles the request in survivable
mode and all applications in the user's application sequence are skipped except for the
Branch Session Manager Administration
Administering Avaya Aura
®
Session Manager November 2010 349
Comentarios a estos manuales