Multiple Session Manager configuration checklist

Last Updated : Sep 01, 2026 |
Prolog information
Task
Notes
Reference
Configure internal and external addresses, corresponding to the primary and secondary Session Managers for the A1 and B1 interfaces.
Create two external signaling interfaces and two internal signaling interfaces.
Create two external media interfaces and two internal media interfaces.
Create a media rule.
Create a server interworking profile.
Ensure that voice sessions are set as per the user license in the application rules and enable video.
Create an endpoint policy group.
Create two server profiles, one for the primary and another for the secondary Session Manager.
Ensure that you enable heartbeat so that Avaya SBC sends heartbeats to Session Manager. The heartbeats are used to detect whether a Session Manager is available.
Create a reverse proxy for file download.
Create two routing profiles for primary and secondary Session Managers.
Do not use alternate routing in a multiple Session Manager deployment.
Do not configure the Next Hop Server 2 field.
Remote worker uses its algorithm to determine when to reach the secondary Session Manager. Avaya SBC does not require alternate routing in this type of deployment if the primary Session Manager goes down.
Create two subscriber endpoint flows corresponding to the primary and secondary Session Managers.
If you require RTP, use default low or avaya-def-low-encoding (for SRTP) depending on the endpoints.
Note:
If RTP and SRTP are both used, select capability negotiation.
Create a server flow.
Create two server flows, one for Session Manager 1 and another for Session Manager 2.
Configure an application relay for IM.
Note:
For more information about remote worker configuration, see Remote worker configuration checklist.