Log in to the EMS web interface with administrator credentials.
On the Device menu, select the Avaya SBC instance.
In the navigation pane, click Network & Flows > End Point Flows.
The application pane displays the list of existing devices, while the content pane provides the subscriber flow and server flow information about the selected device.
Click the Server Flows tab and click Add.
The application pane displays the Add Flow window.
In the Flow Name field, enter a name for the server flow.
In the SIP Server Profile field, select the core server.
In the Received Interface field, select the interface all Branch Session Managers connect.
In the Signaling Interface field, select the signaling interface.
A unique signaling interface should be created for each Branch Session Manager.
In the Media Interface field, select the media interface.
In the Routing Profile field, select the routing profile that routes to Branch Session Manager.
In the Remote Branch Office field, select the the next hop Branch Session Manager.
This field is the key to route the messages from Session Manager to Branch Session Manager. Avaya SBC uses SNI information in route and this field to route the message to correct Branch Session Manager.
In the Topology Hiding profile field, set the appropriate value depending on the server.
This field changes the SIP message headers sent to the next hop server.