Avaya POM Pluggable Data Connector POM PDC

The Proactive Outreach Manager Pluggable Data Connector ( POM PDC) is a Dialog Designer or Avaya Aura ® Orchestration Designer plug-in and extends the Dialog Designer or Avaya Aura ® Orchestration Designer application’s capability to interface and integrate with Proactive Outreach Manager (POM) using the core functionality of the PDC framework. It implements the functionality of seamless connectivity with POM for various type of data exchange, and establishes a connection between the VXML application and the POM server for information access and update. The PDC is similar to the Connection Technology Inc (CTI) connector and the IC connector. It extends the functionality of the Data node palette of Graphical Call flow editor in Dialog Designer or Avaya Aura ® Orchestration Designer, and provides following nodes to execute custom action for POM servers:

  • Update disposition
  • Add contact info
  • Add contact to running job
  • Get contact info
  • Update contact attribute
  • Get contact attribute
  • Add to DNC List
  • Remove from DNC List

Avaya POM 3.1 Features Descriptions

Avaya Proactive Outreach Manager (POM) is a managed application of Avaya Aura ® Experience Portal, a new class of application, linking the capabilities within the platform more closely with the management infrastructure and services. POM provides a solution for unified, multichannel, inbound and outbound architecture with the capability to communicate through different channels of interaction like Short Message Service (SMS), or e-mail, or traditional voice and video.


  1. Campaign management
  2. Contact list management
  3. Attribute management
  4. Data sources
  5. Media channel management
  6. Campaign strategy management
  7. Campaign restrictions
  8. Pacing management
  9. Do Not Call list management
  10. Web service management
  11. Pluggable Data Connector nodes
  12. Multitenancy


A campaign delivers a specific message to all customers in the database through selected channels such as e-mail, SMS, and voice.

POM provides a Web-based wizard to create campaigns. A campaign typically has a name, a campaign strategy, and one or more contact lists. You can have either a finite campaign or an infinite campaign. You can set filter criteria on the contact lists. If you specify a filter criterion, POM applies the criterion at the beginning of a campaign and selects only those customer records that meet the specified criterion. You can define and associate one or more custom completion codes with a campaign when you need some user input.

You can set criteria to terminate finite campaigns. For example:

  • Goal-based campaign: A goal-based campaign terminates after receiving an expected number of responses from customers.
  • Time-based campaign: A time-based campaign terminates after running for a specific time duration. For example, you can terminate a campaign after 12 hours.
  • Completion code-based campaign: A completion code-based campaign terminates after achieving a specific completion code condition. For example, you can terminate a blood donation campaign after you receive 50 accepted responses.
  • Natural finish: A natural finish campaign does not have specified finish criteria and terminates naturally after processing the customer records.


Campaigns need phone numbers for making phone calls and sending SMSs and email
addresses for sending email messages. A contact list is a logical collection of customer
records. You can set up any number of contact lists and associate one or more contact lists with a campaign. You can also use a single contact list in multiple campaigns. In a multitenant environment, you can associate a contact list with one or more tenants. Typically this customer data resides outside POM in a contact management system, and based on your campaign requirements, you must import relevant customer records into POM at regular time intervals.

You can set up any number of contact lists and define any number of attributes. Using POM, you can import customer records into a contact list from various external data sources such as flat files, external database and use various Web service methods to create, read, and update customer records. You can export all customer records into a comma-separated values (.csv) file.


Attributes are properties of customer data.

Based on your campaign needs, you might need custom attributes such as Amount Due, Due Date, and BloodType. Using POM you can set up custom attributes, and import data to these attributes. A typical custom attribute has a name, data type, and privacy flag. The privacy flag helps you to define the visibility of this attribute in a multitenancy setup.


With data sources, you can organize customer records into a contact list. You can define two types of data sources, file based and database based. With the file-based data source, you can import customer records from a .csv file into a contact list. The .csv file can either be on a local file system or the File Transfer Protocol (FTP) server. With the database-based data source, you can import customer records from an external database. You can run the data source to import data. You can also define recurring schedules to import data at a fixed interval from an external file or a database.


POM uses various notification channels to run campaigns: SMS channel, email channel, and voice and video channel.

Email support only text and multiple attachments.


ou can use the Pluggable Data Connector (PDC), a plug-in, to gain access to POM specific operations using Voice Portal or an Avaya Aura ® Orchestration Designer application.


Avaya POM Postgres DB Connect Command

[email protected] 08:04 PM /opt/Avaya/avpom/POManager/logs # su – postgres

-bash-3.2$ psql
Welcome to psql 8.3.10, the PostgreSQL interactive terminal.

Type: \\copyright for distribution terms
\\h for help with SQL commands
\\? for help with psql commands
\\g or terminate with semicolon to execute query
\\q to quit

postgres=# \\c VoicePortal
You are now connected to database “VoicePortal”.

pom=# select * from pim_job where job_id=’1150′;
job_id | campaign_id | schedule_id | status | start_time | end_time | last_allocated_id | f inish_reason | next_archival_time | abort_time | total_calls | total_emails | total_sms | total_contacts | successful_calls | nuisance_calls | customer_hangups
1150 | 1 | | 16 | 2011-03-02 12:41:42.188-07 | | -1 | | | | 0 | 0 | 0 | 0 | 0 | 0 | 0
(1 row)

pom=# delete from pim_job where job_id=’1150′;

Src: How to stop POM Campaign manually


[email protected] ~]# service POM restart
Stopping POM at Mon Oct 17 10:12:07 CEST 2011
Stopping individual components:
Stopping Campaign Manager…
Stopping Campaign Manager:
Warning: No CM process is running! Please restart CM [ OK ]
… successful
Stopping Campaign Director…
Stopping Campaign Director:
Warning: No CD process is running! Please restart CD [ OK ]
… successful

POM Shutdown Status: [ OK ]

Solution: From the Voice Portal (VP) web Administration page, remove and create back the POM server.

From the Voice Portal Web Administration page, access menu POM Configuration / POM servers

  1.  Check the box in front of the POM server name and click the Delete button.
  2. Click the Add button to create back the POM server and fill the POM Server Name and POM Server IP Address fields.


 Proactive Outreach Manager POM: Got only one ring on POM dialed contact

When running the campaign, the called contacts ring only once. In the POM report, the calls are identified as transferred however the calls have not been answered. The strategy has been developed to use the AvayaPOMAgent application which proceed with a Blind transfer.

On CM, access the administration and run:

change system-parameters special-applications.

Set to yes SA8874 as shown below:

(SA8874) – Call Status Messages for 7434ND IP Softphone? y

[[email protected] ~]# service POM status


Avaya POM Components

POM Experience Portal Management System (EPMS) Plug-in
When POM is installed, the POM plug-in is installed on the Experience Portal. This plug-in incorporates the POM Web application and POM tools that look after licensing, logging, and alarming.

POM integrates with the EPM to provide common administration and management tasks like Single Sign On (SSO), user management, logs, alarms and license management. The POM plug-in is only installed on the primary EPM.

When the EPMS plug-in is installed, the plug-in registers POM as a managed application with Experience Portal, deploys the POM Web application on the Tomcat server and initializes POM related configurations.

POM Server
The POM server consists of core POM components required to execute campaigns and communicate with the various POM Web services. The POM server can be installed on  either the primary EPM or auxiliary EPM. When installed on more than one hardware server, the POM server supports high availability and failover capabilities.

Campaign Director

Campaign Director is a Linux service responsible for triggering campaigns and data imports at scheduled date and time. Campaign Director is also responsible for pausing and resuming campaigns based on user action and terminating campaigns if their finish criteria are specified. When POM is installed in a multiple server configuration, only one Campaign Director is in the active state and others are in the dormant state. For a multiple server configuration, the Campaign Director is responsible for assigning the contacts to be processed for any campaign across POM servers. Campaign Director is also responsible for redistribution of load in case of failures.

POM Web services

Web services are installed as part of the POM server and are accessed from the external applications. POM Pluggable Data Connector (PDC) uses Web services to interface with POM. Web Services can be used to access various contact attributes to play personalized prompts or make certain decisions in the application flow.

Agent Manager

POM Agent Manager (PAM) is a Linux service installed with the POM server and is a core module to manage and run agent-based and agent-less campaigns. The PAM is responsible for distributing licenses to all voice based campaigns. The high-level functions of PAM include:

  • Manages agent allocation and state for campaigns
  • Manage agents in a blended job. This module is only supported in Call Center Elite
  • Update the POM database with current agent related information for reporting
  • Distribute the preview and predictive agent licenses among running agent-based campaigns and distributing outbound ports to voice notification campaigns
  • Support real time commands from POM Monitor like changing job-related parameters minimum agents, priority or agent based commands like Forced Logoff

POM Single Server Configuration

A single server deployment can be used for smaller capacity deployments (up to 75 Predictive agents).The illustration below depicts the single server configuration.

When using the single-server configuration, a separate server will be required for failover. The configuration includes a single server running the EPM, Media Processing Platform (MPP), POM software along with the database and application server. For single server installation, the POM server and EPM plug-in packages are installed on the primary EPM.

POM Multiple Server Configuration

The multiple-server configuration includes one or more POM servers installed on the primary EPM and auxiliary EPM. The EPMS plug-in resides only on the primary EPM and the rest of the POM servers reside on the auxiliary EPM systems. In this configuration, one of the designated POM servers controls the failover and load balancing when using the agent-less notifications. The following diagram shows a multiple-server configuration. For simplicity, the MPPs and App Servers/Speech Servers are excluded in this diagram.

For scalability, POM can be configured with multiple POM Servers and Auxiliary EPMs with multiple MPPs. They can all be served from the same external database server. The database server is used for the contact lists, campaigns, strategies, reports, and other critical data.
When executing campaigns in this configuration, the Campaign Director distributes the load across the POM Servers. When one of the Campaign Directors configured as the Master Campaign Director crashes, the Campaign Director on another POM Server that was initially in dormant state automatically becomes the Master. If a particular POM Server crashes, after a certain interval the Master Campaign Director reallocates the active campaign on the crashed POM Server to another POM Server. If multiple EPMs are available for a campaign, the POM Server uses all EPM Servers for load balancing and failover. POM uses the EPM outbound Web service to launch a call.


Avaya POM Features and Benefits Summary


POM 3.0.1 positioning in Avaya’s Outbound Portfolio

Avaya có 3 giải pháp outbound chính, đó là:

  • Avaya Outbound Contact Express 1.0
  • Avaya Proactive Contact 5.1.1 (PCS)
  • Avaya Proactive Outreach Manager 3.1 (POM)

Selecting the Optimus Avaya Outbound Solution


3 Lợi ích của Avaya Proactive Outreach Manager

POM provides 3 benifits as following:


Increase revenue, reduce live agent costs, manage receivables, manage customer relationships proactively, retain existing customers and acquire new customers

  • High application productivity through maximum live connects
  • Advanced list management with customer segmentation
  • Utilize campaigns with media/resource escalations from low-cost emails to high-touch Predictive dialing such that right-party connects are achieved at the lowest costs

Improve efficiencies over outsourced business processes

  • Control campaign priorities and inbound queues


Contact maximum customers, reduce live agent costs, generate new/additional revenue, and report on your results

  • Improve agent productivity by proactively channeling customers to self-service
  • Maximize revenue through industry-leading call classification technology Simple and comprehensive real-time and historic reporting on business activities
  • Reliably comply with applicable regulations
  • Maximize operational efficiency with a robust and stable system

Comply with Do-Not-Call regulations by utilizing (DNC) list management features of the
application and guard time protection

Comply with applicable regulations by recording the calls where live agents speak to live customers

Increase agent administration efficiency by administering all agents through a single CC- Elite administration interface

Design complex campaigns including agent-less and agent-based outreach easily


Meets business group’s objectives, fits well with your existing infrastructure and can grow to meet your evolving needs

  • Integrated solution from Avaya, integrating with AAEP/CC-Elite/Avaya WFO for Call Recording

Highly secure and reliable solution with low maintenance costs

  • Low downtime and low maintenance cost to reduce total cost of ownership
  • Customer data is protected within the database with role-based access only

Vendor provides end-to-end professional services during installation as well as throughout the life of the solution

  • Avaya APS and authorized business partners for end-to-end management of the implementation globally
  • Avaya Global Support Services (GSS) and authorized business partners for
    maintenance and support globally



Giới hạn cuộc gọi trên tổng đài Avaya

Thiết lập một số thông số sau:

  • Outgoing Trunk Disconnect timer = 8 min in COR of trunk
  • Trunk COR for Outgoing Trunk Disconnect? = y in system-parameter feature
  • Try the COR for the user/station.
  • Affects outgoing public network trunks (CO, DIOD, FX, WATS, and ISDN public-network). If the Alcatel ISDN-PRI trunk group is a TIE type, then it’s not considered a Public Network trunk and won’t be eligible for the “Outgoing Trunk Disconnect Timer” feature.

[email protected]


Sự khác biệt giữa các loại quay số Preview, Progressive, Predictive trong cuộc gọi outbound

Trong các trung tâm chăm sóc khách hàng việc chăm sóc khách hàng tập trung phần lớn vào các dịch vụ inbound. Đối với loại hình dịch vụ chăm sóc khách hàng việc sử dụng các cuộc gọi outbound cũng rất cần thiết để tăng sự thỏa mãn khách hàng hay mở rộng các chiến dịch chủ động từ DN đến khách hàng của họ.

Về mặt kỹ thuật cũng có nhiều kỹ thuật quay số cuộc gọi ra từ trung tâm chăm sóc khách hàng. Trong bài này tôi sẽ mô tả 3 loại quay số phổ biến nhất.

Cách dịch vụ outbound hay được biết đến thông qua POM (Proactive Outreach Manager) của Avaya.


Ở chế độ này agent có quyền xem trước các thông tin cuộc gọi trước khi click to call. Và tất nhiên agent của thể bỏ qua cuộc gọi trong list để đến cuộc gọi tiếp theo.

Việc này sẽ tăng thời gian xử lý cuộc gọi. Phù hợp với các việc kinh doanh phức tạp, nội dung cuộc gọi linh hoạt.


Agent sau khi thực hiện cuộc gọi sẽ có thời gian Wrapup và Available lại, khi agent available lại hệ thống sẽ tự động thực hiện cuộc gọi tiếp theo mà không có thời gian nghỉ cho agents.

Ưu điểm là thời gian nhanh, số lượng cuộc gọi thực hiện lớn, nội dung cuộc gọi giống nhau (không có sự khác biệt lớn giữa các cuộc gọi).


Cuộc gọi chỉ thực sự kết nối khi khách hàng ở đầu dây bên kia trả lời cuộc gọi, điều này giúp tiết kiệm thời gian chờ của tư vấn viên.

Sử dụng trong các trung tâm CC có số lượng cuộc gọi lớn, sự chuyên nghiệp của tư vấn viên, chi phí cho mỗi cuộc gọi cao.

Tham khảo:


Avaya Scopia Management Specification

Scopia Management provides a comprehensive management, control and scheduling solution to efficiency administer and enable easy-to-use video conferencing.


That is:

  1. Unified Central Management
  2. Endpoint and Network Device Management
  3. Virtualizes Conferencing Resources
  4. Unified Communication Integration
  5. Manage Access and Cost with detailed reports