Checklist for configuring Geographic-redundant deployment

Last Updated : Apr 25, 2023 |

Use the following checklist to configure the Geographic-redundant Avaya SBC deployment.

Note:

All Avaya SBC devices in a Geographic-redundant Avaya SBC deployment must be controlled by the same external EMS.

In the following checklist:

  • The IP address on Avaya SBC towards the internet is referred to as external address.

  • The IP address on Avaya SBC towards the core network or call server is referred to as internal address.

  • The primary Session Manager is referred as SM1 and the secondary Session Manager is referred as SM2.

Task

Reference

Notes

Configure internal and external addresses corresponding to primary and secondary Session Manager devices for the A1 and B1 interfaces.

Configuring internal and external IP addresses

Create two external signaling interfaces.

Creating an external signaling interface toward phone network

Create two internal signaling interfaces.

Creating an internal signaling interface toward Avaya call server

Create two external media interfaces.

Creating an external media interface toward phone network

Create two internal media interfaces.

Creating internal media interface toward Avaya call server

Create a server interworking profile.

Creating a server interworking profile

Create two server profiles, one for the primary and another for the secondary Session Manager.

Creating an Avaya call server profile

Create PPM Mapping Profiles for each group of remote workers that has the same pair of Session Managers as primary and secondary Session Manager.

Administering Avaya Session Border Controller

Configure reverse proxy service for downloading file or firmware.

Creating reverse proxy service for file or firmware download

Create an endpoint policy.

Creating an endpoint policy

Create two routing policies for SM1 and SM2.

Creating a routing profile to Avaya call server

Create two subscriber endpoint flows corresponding to the primary and secondary Session Managers.

Creating a subscriber flow .

If you require RTP, use the 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 two server flows corresponding to the primary and secondary Session Managers..

Creating a new server endpoint flow

Create application rules.

Creating application rules

Ensure that voice sessions are set as per the user license in the application rules and enable video.

Configure application relay for IM.

Configuring application relay for IM

Create a reverse proxy service for PPM traffic.

Creating a reverse proxy service for PPM traffic

Configure web collaboration.

Configuring Avaya SBC for web collaboration

If the Session Manager Firewall is enabled, add the Avaya SBC Internal IP in the Whitelist.

Configure Presence Services.

Configuring Presence Server