Solution pre-requisites and considerations

Last Updated : Apr 03, 2024 |

Consider the following for deploying the solution:

Table 1: Solution pre-requisites

Requirement

Description

Agents must be SIP agents.

To work with Avaya Experience Platform™ (On-Prem + Connect), you must convert the H323 extensions to SIP.

Agents must log on to Avaya Workspaces only.

  • The offer is WebRTC only.

  • Multiple Device Access (MDA) setting must be 1.

  • No support for other softphone or hardphone configuration.

One Avaya Experience Platform™ Public Cloud tenant supports one Avaya Aura® system.

One Avaya Aura® system is one Avaya Aura® System Manager (or System Manager (primary + secondary pair)) and the elements managed by it.

If an enterprise has two or more separate System Managers, the System Managers and the elements mapped to them must integrate with Avaya Experience Platform™ (On-Prem + Connect) as distinct Avaya Experience Platform™ Public Cloud tenants.

Important:

For Avaya Aura® System Manager Release 10.1.x, update your system to System Manager Release 10.1.3.1 with the latest published hot fix from PSN006088U: https://support.avaya.com/css/public/documents/101086975

One System Manager manages multiple Avaya Aura® Communication Managers and Avaya Aura® Session Managers.

Support for multiple Communication Managers in the same Data Center and the Communication Manager Survivable Server Core for two or more Data Centers.

The reference architecture for an Avaya Aura® deployment with Survivable Server Core includes two Avaya Hybrid Cloud Gateway clusters.

The capacity limit is 10,000 hybrid voice agents for each Avaya Experience Platform™ Public Cloud cluster and 5,000 for each Communication Manager.

Avaya Experience Platform™ Public Cloud resources share the capacity.

Minimum versions supported.

  • Minimum Avaya Aura® version is 10.1.3.

  • Minimum Avaya Aura® Device Services version is 10.1.1.2.

  • Minimum SAL Gateway version is 4.1.

Minimum number of Avaya Hybrid Cloud Gateway nodes is two (1+1 redundancy) nodes.

Number of nodes required increases depending on the number of agents.

Avaya Hybrid Cloud Gateway requires VMware ESXi 7.0 or 8.0.

Customer's Avaya Aura® deployment provides the E911 configuration.

No in-built E911 provider and Avaya Experience Platform™ (On-Prem + Connect) integration. The E911 Voice channel service of Avaya Experience Platform™ (On-Prem + Connect) is not applicable for Hybrid Voice channel.
Important:

Before implementing Avaya Experience Platform™ (On-Prem + Connect), validate that your SIP agents perform basic agent scenarios in the Avaya Experience Platform™ On-Prem contact center, such as accepting calls, making calls, transferring calls, Go Ready, After Call Work (ACW), AUX, and setting call work code using an existing SIP agent client such as Avaya Agent for Desktop (SIP) or Avaya Workplace Client.