
4. If required, create a sequence of applications (application sequence) and specify
call handling by CM-FS/ES which should be the same one as specified on the BSM
Instance form.
5. Administer users using the BSM as the Survivability Server.
Adding a SIP entity as a Branch Session Manager instance
Before you begin
Before starting this procedure, make sure that the SIP entity that you want to add was created.
For a Session Manager type SIP entity, the customer has to administer the listen ports on the
SIP entity form. These listen ports are used by endpoints to connect to Branch Session
Manager and they can be used to map different ports to different domains.
Procedure
1. On the System Manager console, under Elements, click Session Manager.
2. Click Session Manager Administration in the left navigation pane.
3. Click New on the Branch Session Manager Instances section of Session Manager
Administration screen. The system displays the Add Branch Session Manager
screen.
4. Under the General section, enter the following information:
• Select the SIP Entity Name from the drop-down list.
• In the Description field for this entity, add a comment if required.
• In the Management Access Point Host Name/IP field, add the IP address of
the host on which the management agent is running; that is, the host on which
the Branch Session Manager is installed.
• Select the Main CM for LSP from the drop-down list. Click the View / Add CM
Entities link to add new CM applications.
• Select the Direct Routing to Endpoints from the drop-down list.
• Select the Adaptation for Trunk Gateway from the drop-down list. This
selected adaptation is used by the Branch Session Manager for routing calls
to or from the Communication Manager LSP trunk gateway.
Note:
In case of Communication Manager Feature Server (CM-FS) or
Communication Manager Trunk Gateway (CM-TG), the adaptation from the
core CM-TG is used by default. This field adaptation selection overrides the
default CM-TG adaptation and is applied to all calls routed on the trunk
gateway entity to the LSP. For Communication Manager Evolution Server
(CM-ES), the default adaptation is taken from the core Communication
Branch Session Manager Administration
Administering Avaya Aura
®
Session Manager November 2010 351
Comentários a estes Manuais