
Communication Manager. When Communication Manager is detected in the sequence, the
request is sent after substituting the LSP's IP address for the core Communication Manager.
So the LSP is automatically used as the Survivable Feature Server.
It is recommended that the Branch Session Manager be configured to support no more than
2 core session managers. Either of the Session Managers can be configured as a primary or
secondary server for a branch user.
Administering Branch Session Manager
Before you begin
The main Communication Manager Feature Server/Evolution Server (CM-FS/ES) is added as
an Inventory item and all appropriate configurations are done for CM-FS/ES in System
Manager. For details, see Administering Avaya Aura
™
Communication Manager Server
Options, 03-603479.
About this task
This section provides the basic steps of Branch Session Manager (BSM) administration.
Procedure
1. Add a SIP Entity for BSM using the IP of the BSM security module.
2. Administer a BSM Instance.
3. Create Entity Links from the BSM to the Main CM server (CM-FS/ES) as per
following information:
a. In case of BSM with CM Feature Server/ Trunk Gateway (CM FS/TG):
• Entity Link 1: BSM to core CM Feature Server
• Entity Link 2: BSM to core CM Trunk Gateway
Each entity link must use the same port and transport as the
corresponding link to the primary Session Manager (SM) in the core. The
ports between the CM and SM entities must be unique.
b. In case of BSM with CM Evolution Server (CM-ES):
A CM-ES can be configured using just one entity link. That entity and
entity link is used for both application sequencing and trunk gateway
routing.
BSM accordingly:
• Creates entity and entity link between the BSM and the LSP for survivability
mode.
• Applies the required adaptations to calls in survivability mode.
Configuring and monitoring Session Manager instances
350 Administering Avaya Aura
®
Session Manager November 2010
Komentáře k této Příručce