Edit online

Pega Call™ 25.1.2 includes fixes for customer-reported and internally-identified issues.

NOTE: This patch requires Pega Platform™ 25.1.2.

Resolved issues in applications on Constellation

Ticket # CTI Title Description
INC-D1715 Avaya AES AddressSnapshot failures fixed Resolved an issue where the system prevented logins to the application due to the AddressSnapshot failures after a migration to Pega Cloud.
INC-C41726 Avaya AES JKS certificate location configuration works as expected Resolved an issue where the system could not properly locate JKS certificates in Pega Cloud environments, preventing the establishment of encrypted connections and causing CTI link failures.
BUG-968088 Avaya AES and Cisco Finesse CTI login issues resolved Resolved an issue where assigning or modifying certain properties resulted in TypeError exceptions and users not being able to log in to the CTI links.
INC-C24487 Cisco Finesse Entries in pr_index_WC_POW_Work no longer duplicate Resolved an issue where the system created duplicated entries in the pr_index_WC_POW_Work index table when agents performed Wrap up.

Resolved issues in applications on UI Kit

Ticket # CTI Title Description
INC-D1715 Avaya AES AddressSnapshot failures fixed Resolved an issue where the system prevented logins to the application due to the AddressSnapshot failures after a migration to Pega Cloud.
INC-C41726 Avaya AES JKS certificate location configuration works as expected Resolved an issue where the system could not properly locate JKS certificates in Pega Cloud environments, preventing the establishment of encrypted connections and causing CTI link failures.
BUG-954273 Avaya AES Pre-passivation activity sets deviceState correctly Resolved an issue during node scaling where the pre-passivation activity failed to set the deviceState status for Web Socket connections, leading to incorrect agent status being displayed across the cluster.
BUG-960626 Cisco Finesse Failed outbound calls to a busy number display a single alert Resolved an issue where the system triggered multiple error messages when outbound calls encountered a busy number, requiring agents to manually dismiss several dialog boxes before continuing their work.