Avaya Proactive Outreach Manager (POM) Integration Overview

The Avaya POM integration is designed to work with active VoIP (using DMCC) as an audio source. Call control and metadata are provided by the Avaya POM dialer.

General architectural example of the Avaya POM integration; the audio source is not shown.
Component Function
Avaya PBX PBX component that controls the audio being presented to and from digital phones, IP phones, or both.
Avaya POM Dials outbound calls. Directs the PBX to connect calls to agents. Sends events (such as CALLCONNECT, CALLDISCONNECT, and so forth) and other data (such as Agent ID) to the Uptivity server.
Uptivity Server

Provides an interface to the Uptivity recording node to start/stop call recording. Generates call records in the Uptivity database that store Agent ID and other information.

Avaya POM is used to design and deploy outbound voice, SMS, and e-mail campaigns. The Uptivity integration with POM requires a DMCC integration for its audio source. Refer to the appropriate guide for the audio source integration for additional knowledge and requirements, available from the Recording Integrations Overview

  • Avaya DMCC-MR
  • Avaya DMCC-SO
  • Avaya DMCC-SSC

The customer is expected to have a working environment with Avaya Proactive Outreach Manager. No specific configuration of Avaya POM components is required to integrate with the Uptivity software.

Terminology

To ensure a common frame of reference, we use the following terms in conjunction with Avaya integrations:

AACC
Avaya Aura Contact Center. AACC is an Avaya contact center product that is common in VoIP environments and in multi-channel call centers due to its support for non-voice interactions.
AES
Application Enablement Services. The AES server in an Avaya contact center hosts software that provides CTI events
Avaya CMS
Avaya Call Management System. This contact center product is designed for businesses with complex contact center operations and high call volume. Sometimes referred to as Avaya CM.
DMCC
Device Media Call Control. This functionality of the Avaya AES and AACC servers provides a means of active recording via VoIP, even for endpoints that are not IP telephones.
POM
Proactive Outreach Manager. POM is an outbound platform (dialer) for creation and management of outbound and blended phone campaigns and customer communications.
TSAPI
Telephone Services Application Programming Interface. Avaya TSAPI is the actual software that provides the call control events and metadata to Uptivity.
S8300, S8500, S8700
These are common models of Avaya PBX equipment.

Customer Responsibilities

Customers are responsible for supplying the physical connection(s), IP connection(s), or both to the Avaya system, as well as for obtaining any licensing required by Avaya. You may also be responsible for configuring Avaya system components to support the recording integration.

Detailed steps for the Avaya configuration can be found in Avaya’s documentation, which is available on the Avaya website or from your Avaya vendor. You should always use the appropriate guides from Avaya to install and configure Avaya components.

Configure Audio Source

Perform any required configuration for the Avaya DMCC audio source integration. Refer to the appropriate guides, available from the Recording Integrations Overview

  • Avaya DMCC-MR
  • Avaya DMCC-SO
  • Avaya DMCC-SSC

Provide POM User Account

Uptivity requires a user account on the Avaya Proactive Outreach Manager to receive events. Whether an existing account is used or a new account is created specifically for this purpose, you will need to provide the username and password to your Uptivity installation team.

Provide POM Server and Port

Uptivity uses the POM server address and port to communicate with the server for metadata and call information. You will need to provide this information to the Uptivity installation team.

POM Administration

Once installation and configuration are completed by the Uptivity installation team, some adjustments may need to be made as your needs evolve. During ongoing use of the system, your Uptivity administrator may need to configure new channels or reconfigure existing channels.

This integration works with active VoIP (using DMCC) as an audio source. If you add or reconfigure channels, you will need to follow any procedures specific to those audio sources as found in the appropriate customer guide. Contact Uptivity Support if assistance is required.

Avaya Requirements

Software

  • Avaya POM Release 3.0 or newer

These requirements are in addition to the audio source requirements; refer to the relevant customer guide for details.

Software and Licensing

No additional software or licensing is needed.

Uptivity Requirements

Hardware, Software, and Licensing

General Uptivity hardware and software requirements are specified in the customer guide for the audio source integration. Those guides also explain the licensing requirements. No additional Uptivity licensing is needed.

Specific hardware and system software required for your implementation is determined by Uptivity Sales Engineering during the discovery and system design process. No system hardware or software should be purchased or requisitioned until the final system design document is complete.

Related Themes

Related Tasks

Related References