Integrating Avaya Experience Platform (On-Prem + Connect) with Avaya Session Border Controller for Enterprise

Last Updated : Oct 17, 2024 |

To integrate Avaya Experience Platform™ (On-Prem + Connect) with Avaya Session Border Controller for Enterprise (Avaya SBCE), following are the network pre-requisites and considerations:

  • Deploy Avaya Hybrid Cloud Gateway in the A1 internal network along with other Avaya Aura® components. Avaya Hybrid Cloud Gateway communicates with Avaya SBCE through the A1 interface. This reduces any additional firewall configuration required for Avaya Hybrid Cloud Gateway to communicate with Avaya SBCE.

    Note:

    Avaya Hybrid Cloud Gateway still needs connectivity with UC3 through internet.

  • The Avaya SBCE B1 media interface configured for Avaya Hybrid Cloud Gateway flows must have a public IP address so that it can communicate directly with Avaya Media Processing Core™ without Network Address Translation.

  • For Avaya Experience Platform™ (On-Prem + Connect) call flows, the on-premise Avaya Aura® Media Server communicates with the Avaya SBCE A1 media interface and does not have direct media connectivity with Avaya Media Processing Core™. Talk path always gets established between the Avaya SBCE B1 media interface and Avaya Media Processing Core™.

  • The Avaya Experience Platform™ (On-Prem + Connect) account being integrated with the on-premise Avaya SBCE must have Media Latching disabled inside the Avaya Hybrid Cloud Gateway element in Application Center Administration.

You can log into the Avaya SBCE Element Management System server to integrate Avaya Experience Platform™ (On-Prem + Connect) with Avaya SBCE.

Task

Description

Create user agents for Avaya Hybrid Cloud Gateway

In System Parameters > User Agents, add a new entry for Avaya Hybrid Cloud Gateway:

  • Name: Hybrid Cloud Gateway

  • Regular Expression: AHCG.*

Create client profiles

Create two client profiles for the A1 and B1 interfaces to use for the Avaya Hybrid Cloud Gateway TLS communication with Avaya SBCE.

For example, client profile hcg-A1-client-profile for the A1 interface and client profile hcg-B1-client-profile for the B1 interface.

Note:

The Avaya SBCE identity certificate used in the client profile must contain the Avaya SBCE FQDN in Subject Alternative Name. Configure the same Avaya SBCE FQDN in the List of SIP Server Addresses field of an Avaya Hybrid Cloud Gateway element in Application Center Administration.

Create server profiles

Create two server profiles for the A1 and B1 interfaces to use for the Avaya Hybrid Cloud Gateway TLS communication with Avaya SBCE.

For example, server profile hcg-A1-server-profile for the A1 interface and server profile hcg-B1-server-profile for the B1 interface.

Note:

The Avaya SBCE identity certificate used in the server profile must contain the Avaya SBCE FQDN in Subject Alternative Name. Configure the same Avaya SBCE FQDN in the List of SIP Server Addresses field of an Avaya Hybrid Cloud Gateway element in Application Center Administration.

Create media interfaces

Create the required number of A1 and B1 media interfaces for the Avaya Hybrid Cloud Gateway call flows.

Create signaling interface

Create the required number of A1 and B1 signaling interfaces for the Avaya Hybrid Cloud Gateway call flows. For Avaya Hybrid Cloud Gateway integration, it is better to have two dedicated A1 signaling interfaces for communication with each Session Manager. For example, A1 IP1 receives SIP signaling from Avaya Hybrid Cloud Gateway. Avaya SBCE forwards this traffic to A1 IP2 and A1 IP2 sends this traffic to Session Manager.

Create Avaya Hybrid Cloud Gateway subscriber flows

To create the Avaya Hybrid Cloud Gateway subscriber flows for Session Manager1 (SM1) and Session Manager2 (SM2), configure the following interfaces:

  • User Agent: Select the user agent Hybrid Cloud Gateway, which you created earlier.

  • Signaling Interface: Assign the signaling interface created earlier for Avaya Hybrid Cloud Gateway.

  • Media Interface: Assign the external media interface created earlier for Avaya Hybrid Cloud Gateway.

  • Routing Profile: Assign the required routing profile mapped with SM1 or SM2.

In the subscriber flow for Avaya Hybrid Cloud Gateway, as shown below, you must configure Methods Allowed Before REGISTER to allow the OPTIONS method. Avaya Hybrid Cloud Gateway always does a keepalive check of the SIP server before initiating PPM download. Also, it is better to have a dedicated A1 signaling interface to receive SIP traffic from Avaya Hybrid Cloud Gateway. You must assign the User Agent created with a regular expression AHCG.* to the Avaya Hybrid Cloud Gateway subscriber flows. If any other client other than Avaya Hybrid Cloud Gateway tries to register to Avaya SBCE using the dedicated Avaya Hybrid Cloud Gateway A1 signaling interface, Avaya SBCE rejects the REGISTER with the 403 Forbidden response.

End Point Flows View Flow

Create Avaya Hybrid Cloud Gateway server flows

To create the Avaya Hybrid Cloud Gateway server flows for SM1 and SM2, configure the following interfaces:

  • Received Interface: Assign the A1 signaling interfaces created for Avaya Hybrid Cloud Gateway with which Avaya Hybrid Cloud Gateway communicates for SM1 or SM2.

  • Signaling Interface: Assign the A1 signaling interfaces created for Avaya Hybrid Cloud Gateway through which Avaya SBCE communicates with SM1 or SM2.

  • Media Interface: Assign the A1 media interface created for Avaya Hybrid Cloud Gateway.

Configure Avaya Hybrid Cloud Gateway and Personal Profile Manager (PPM) mapping profiles

To create the Avaya Hybrid Cloud Gateway and PPM mapping profile for SM1 and SM2, configure the following fields:

  • Server Address: The asset of SM or security module Fully Qualified Domain Name (FQDN) with port 5061.

  • Signaling IP Address: The Avaya SBCE A1 interface with port 5061 to which Avaya Hybrid Cloud Gateway communicates for PPM requests.

Important:

While creating a PPM mapping profile for the SIP Server Profile field and the SBC Device field, select the Custom check box to specify the Server Address/Port and the Mapped IP/Port. This enables Avaya Hybrid Cloud Gateway to send any further PPM and SIP messages to Avaya SBCE.

Configure reverse proxy

Configure reverse proxy for SM1 and SM2 for PPM downloaded by Avaya Hybrid Cloud Gateway.

  • Listen IP: The A1 interface IP of Avaya SBCE to which Avaya Hybrid Cloud Gateway communicates for PPM requests on port 443.

  • Listen Protocol: Configure the Listen Protocol field as HTTPS.

  • Listen Port: Configure the Listen Port field as 443.

  • PPM Mapping Profile: Assign the correct PPM profile created for Avaya Hybrid Cloud Gateway.

  • Connect IP: The A1 interface IP of Avaya SBCE through which Avaya SBCE communicates with Session Manager for PPM requests.

  • Ensure to assign the correct Listen TLS Profile and Server TLS Profile created for Avaya Hybrid Cloud Gateway.

  • Server Address is the asset of Session Manager or security module FQDN.

Configure Avaya Hybrid Cloud Gateway

To configure Avaya Hybrid Cloud Gateway, do the following:

  1. Log in to Session Manager.

  2. Navigate to  > Elements > Routing > SIP Entities.

  3. Add SIP Trunk as the SIP entity type with the Avaya SBCE A1 interface IPs or FQDNs from which Avaya SBCE forwards the Avaya Hybrid Cloud Gateway traffic to Session Manager.