Avaya Experience Portal (AEP) 8.1

This guide explains how to configure Capacity Private Cloud ASR and TTS as speech servers for Avaya Aura Experience Portal (AAEP) 8.1. Experience Portal reaches the platform's speech services over MRCP v2, and AAEP 8.1 recognizes the platform as a native LumenVox engine type — so, unlike the older 7.0.x integration, there is no need to register the servers under a generic Nuance profile. The work has three parts: apply two Media Server settings, add the ASR and TTS speech servers in the AAEP management console, and reference them from your application.

A note on testing. The platform's ASR and TTS cannot be tested directly from the Orchestration Designer Application Simulator. Deploy applications built in Orchestration Designer to AAEP and test them there.

Prerequisites

  • An installed and licensed Avaya Aura Experience Portal 8.1 server.
  • A working Capacity Private Cloud installation, with ASR and TTS installed and verified independently before integrating with AAEP.
  • Network reachability from the AAEP host to the speech host on the MRCP v2 port (TCP 5060).

For installing the speech services, see Installing the Media Server.

Configure the Speech Platform

Apply the following changes to the Media Server configuration. Both settings are made in the MRCP-API Docker image, in the Media Server configuration file:

mrcp-api/docker/lumenvox/media_server.conf
  1. Set compatibility_mode to 1.
  2. Set reuse_sip_tcp_socket to 1.

Configure the AAEP Speech Servers

In the AAEP management console, add the ASR and TTS as speech servers under System Configuration > Speech Servers. The settings below highlight the values that deviate from AAEP's defaults — set these carefully.

ASR Speech Server

  • Enabled: Yes
  • Engine Type: LumenVox
  • Network Address: <IP of the host running the platform>
  • Base Port: 5060
  • Total Number of Licensed ASR Resources: <number of licenses installed>
  • New Connection per Session: Yes
  • Languages: en-US
  • Ping Interval: 15
  • Response Timeout: 4
  • Protocol: MRCP V2
  • Transport Protocol: TCP
  • Listener Port: 5060

Figure 1: Sample ASR configuration on the AAEP 8.1 Speech Servers page.

TTS Speech Server

  • Enabled: Yes
  • Engine Type: LumenVox
  • Network Address: <IP of the host running the platform>
  • Base Port: 5060
  • Total Number of Licensed TTS Resources: <number of licenses installed>
  • New Connection per Session: Yes
  • Languages: en-US
  • Ping Interval: 15
  • Response Timeout: 4
  • Protocol: MRCP V2
  • Transport Protocol: TCP
  • Listener Port: 5060

Figure 2: Sample TTS configuration on the AAEP 8.1 Speech Servers page.

Configure the Application

When configuring an application to use the platform's ASR and TTS:

  1. Select the ASR and TTS servers you added in the application's Speech Servers drop-downs. Because the Engine Type is LumenVox, they appear under that name.
  2. Under Speech Parameters, set Speech Complete Timeout to a non-zero value — 800 ms is recommended (the default is 0). Leave the remaining speech parameters blank to use their defaults.

AAEP 8.1 Change Application page with the LumenVox ASR and TTS selected and Speech Complete Timeout set to 800

Figure 3: Assigning the configured ASR and TTS servers to an application.

AAEP application Speech Parameters with Speech Complete Timeout set to 800 milliseconds and all other fields blank

Figure 4: Application Speech Parameters. Speech Complete Timeout is set to 800 ms; all other parameters are left at their defaults.

Testing the Integration

Configure the AAEP built-in Test App application to use the platform's ASR and TTS, as shown above, then place a call into the system to verify ASR and TTS functionality.

Related Articles

Was this article helpful?