Change History

Last Updated : Jun 03, 2026 |

Issue

Date

Summary of changes

4.1

November, 2025

The following alarms are added or updated:

  • P_POMWS118

  • P_POMLM001

  • P_POMLM003

  • P_POMLM002

  • P_POMAGT49

  • P_POMAGT50

  • P_POMAGT24

  • P_POMLM004

  • P_POMCD922

  • P_POMCD923

  • P_POMCD924

  • P_POMALM03

The following topics are added or updated:

  • Data stream breaks

  • Authorization failure

  • POM manager and Supervisor Dashboard become inaccessible when Connection to the database fails

  • A reference file for configuring Kafka properties

  • The System Load tab on the POM Health Monitor page displays no data for the PostgreSQL users

  • Resolving the error occurred by a corrupt zookeeper log file that prevents the start of ZooKeeper services

  • Resolving error occurred while enabling Kafka High Availability

  • Kafka HA does not enable after switchover

  • POM displays incorrect language

  • Error while saving a campaign strategy when you replace the default Avaya Agent node in a simple call type campaign strategy

  • POM monitor or cache service information removed from the document entirely.

Release 4.0.2 SP2, Issue 1.2

October 2023

The following topics are added:

  • POM fails to export the contacts in the contact list.

  • Fail to Connect to separate database for POM Reports

  • Configuring Transactional logs per Agent

  • Enabling POM server to generate transactional logs per agent

  • Configuring Agent API Transaction logs for Workspaces for Elite client desktop

  • Configuring Agent API Transaction logs for Agent client desktop created using .NET SDK or JAVA SDK

  • Delay in the display of customer details on Agent’s screen in preview campaign

  • Delay in processing retries due to custom result processor

  • In an agent based campaign, the agent hears a static sound after the outbound call completes

  • Workspaces agent is unable to nail up due to the network failure of the primary POM server.

Release 4.0.2 SP 1, Issue 1.1

March 2023

The following topics are added:

  • Capturing POM Configuration using the pomcapture tool.

  • Kafka service does not start on the primary POM server whenever all the auxiliary POM services are stopped.

Release 4.0.2, Issue 1.0

October, 2022

The following topics are added:

  • P_POMWS044

  • P_POMWS046

  • P_POMWS081

  • P_POMWS082

  • P_POMWS083

  • P_POMWS084

  • P_POMWS085

  • P_POMWS086

  • P_PIMWS087

  • P_POMWS088

  • P_POMWS089

  • P_POMWS090

  • P_POMWS091

  • P_POMWS092

  • P_POMWS093

  • P_POMWS094

  • P_POMWS095

  • P_POMWS096

  • P_POMWS097

  • P_POMWS098

  • P_POMWS099

  • P_POMWS100

  • P_POMWS101

  • P_POMWS102

  • P_POMWS103

  • P_POMWS104

  • P_POMWS105

  • P_POMWS106

  • P_POMWS107

  • P_POMWS108

  • P_POMWS109

  • P_POMWS110

  • P_POMWS111

  • P_POMWS112

  • P_POMWS113

  • P_POMWS114

  • P_POMWS115

  • P_POMWS116

  • P_POMAGT09

  • P_POMAGT16

  • P_POMAGT42

  • P_POMAGT53

  • P_POMAGT63

  • P_POMAGT64

  • P_POMAGT65

  • P_POMAGT66

  • P_POMAGT67

  • P_POMAGT69

  • P_POMAGT70

  • P_POMRTR26

  • P_POMKF003

  • P_POMSDK02

  • P_POMALM01

  • P_POMADM01

  • P_POMCA003

  • P_POMDA002

  • P_POMCM041

  • Instructions to troubleshoot a scenario where the POM system displays an error message because the number of attributes exceed the maximum number of attributes.

  • Instructions to troubleshoot a scenario where the POM server does not receive enriched attempts and hearbeat events after stopping the Kafka server

  • Instructions to troubleshoot the POM database if POM displays the following error messages:
    • HikariPool-1 - Connection is not available, request timed out after XXXXX ms

    • Hikari Interrupted during connection acquisition

    • com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: FATAL: sorry, too many clients already

    • FATAL: database "pomopdb" does not exist

    • Caused by: org.postgresql.util.PSQLException: Connection to <DBHOSTIP>:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections

  • Instructions to troubleshoot a scenario where POM displays an internal server error while updating information in a contact list.

  • Instructions to troubleshoot a scenario where POM delivers a nail up call even when an agent is on another inbound call.

  • Instructions to troubleshoot a scenario where the call node scrollbar does not work in the Campaign Strategy Editor window.

  • Instructions to troubleshoot a scenario where a user does not receive a cluster ID.

The following topics are updated:

  • In the Format of the POM log files topic, the Campaign Director abbreviations table is updated with categories that apply to the Campaign Director

  • Overcoming slow dialing

  • Failed to configure an operational database

  • org.hibernate.exception.GenericJDBCException: Cannot open connection

  • Data Stream Has Been Broken

  • Events for Administration, Campaign Director, Campaign Manager, Web services, Agents, ActiveMQ, Report, Router, and Rule Engine

For POM release 4.0.2 service pack 2, the following topics are added:

  • Instructions to troubleshoot a scenario where an export operation tha is in progress gets terminated and POM displays an an error message and fails to complete the export.