The following are the basic steps for administering a Branch Session Manager.
Before you begin
Using System Manager, administer the main Communication Manager Feature Server or Evolution Server (CM-FS/ES) as an Inventory element. For information and procedures, see Administering Avaya Aura® System Manager on the Avaya support site.
Procedure
Add a SIP Entity for the Branch Session Manager using the IP address of the Branch Session Manager Security Module.
Using the System Manager Web Console, administer a Branch Session Manager Instance on the Session Manager Administration page.
Create an entity link between the Session Manager and the Branch Session Manager.
If you are using more than one Session Manager, create a separate entity link between each Session Manager and the Branch Session Manager.
Create an entity link between the Branch Session Manager and the main Communication Manager server.
Ensure that the Communication Manager is the main Communication Manager of the SRS that is linked to the BSM.
The Branch Session Manager uses the administered entity link to the main Communication Manager to internally generate an entity and entity link connection to the Survivable Remote Server (SRS). The system uses the connection for survivability mode.
If Communication Manager is configured as a Communication Manager Feature Server or Trunk Gateway (CM FS/TG):
Create an entity link between the Branch Session Manager and the core Communication Manager Feature Server.
Create an entity link between the Branch Session Manager and the core Communication Manager Trunk Gateway.
If Communication Manager is configured as a Communication Manager Evolution Server (CM-ES):
You can configure a CM-ES using just one entity link. The system uses the entity and entity link for both application sequencing and trunk gateway routing.
Each entity link must use the same port and transport as the corresponding link to the primary Session Manager in the core. The ports between the Communication Manager and Session Manager entities must be unique.
If required, create a sequence of applications (application sequence). The Communication Manager application you select should be the same as specified on the Branch Session Manager administration page.
Note:
If Branch Session Manager is used only for routing purpose with only H.323 (non-SIP station) setup, then administration of application and application sequence is required. If application sequence is not administered, then the link between the SRS and Branch Session Manager will not work as expected.
Administer SIP user profiles using the Branch Session Manager as the survivability server.
Configure the SRS that you linked to the BSM when deploying the BSM.
