Release highlights

RabbitMQ credentials are now required during the installation/upgrade process.

For version 9.5.6 and higher, the installer requires a username and password for the RabbitMQ connection. These credentials will be used to federate the queues between servers and send messages to RabbitMQ.

To learn more, see (9.1+) Installation process or (9.0+) Upgrade process.

When logging in to the Launchpad (<host>/eyequeue) for the first time, the default "admin" user will be required to set a new password.

If the password for the admin user has not been changed since the initial installation of On-Premise Callback, you will be prompted to change the password on the next login attempt.

The NGINX proxy package for secure (HTTPS) installations has been updated to accept TLS 1.3.

The package can be found the \\Virtual Hold Technology\proxy directory. TLS 1.2 is still supported in the new package.

For enhanced security, the Smart Rules user account must now be configured manually.

In order to ensure account security, Smart Rules user credentials are no longer configured by the On-Premise Callback installer, and must now be configured manually after installation.

For instructions on configuring user credentials, see (9.1+) Installing Smart Rules.

Fixed issues

(EEQ-100906) Operation Modes will appear in the Operation Schedules dropdown menu once again.

An update introduced in Google Chrome Version 134+ caused the Operation Schedules dropdown menu not to populate Operation Modes. We have removed dividers from the menu to resolve the issue.

(EEQ-100351 / OPC-1293) An issue causing the Return Call Hold Time report not to populate data in a specific scenario has been resolved.

Due to an update made to the QDump table in the VHT_RPT database, the Return Call Hold Time report could not be generated for individual queues with names containing underscores (_) or spaces. We have updated the report to resolve this issue.

(EEQ-98805) A failure to send email notifications for system failovers will no longer prevent subsequent failovers.

When a network issue prevented email notifications from being sent for system failovers initiated on the System Management page, subsequent failovers would not be completed. Instead, users would see an error message stating "System Management service to perform requested action 500". With this update, a failed email notification will not affect the functionality of system failovers.

(EEQ-98261 / OPC-1252) The status of the VHT_Management_API service on a primary Management server no longer affects the functionality of the same service on a secondary Management server.

Previously, if the primary VHT_Management_API service in a high-availability site was not running, users could not log into the Launchpad on the secondary Management server. Now, the secondary service no longer depends on the primary.

(OPC-1305) We have improved the resilience of the Core Monitor service startup process.

In rare cases, the Core Monitor site.config file could be formatted incorrectly, resulting in critical startup configuration being missed for the VHT_Core_Monitor service. We have updated the way that the site.config file is processed during startup to account for this scenario.

(OPC-1297) Widget stability has been restored after a recent Ruby upgrade.

An update introduced with the upgrade to Ruby version 3.2.0 could cause issues with the Cloud Connector, resulting in widget failures. We have updated the Cloud Connector version file to resolve the issue.

(OPC-1205) An issue that could cause a large number of callbacks to be dialed unexpectedly has been resolved.

When a site was under heavy load with high network latency, a queue-position timer could expire, causing the positions of pending callbacks to reset. This in turn would cause many callbacks to launch at once. We have updated the logic behind resetting the timer so that it does not reset under these conditions.

(OPC-1235) The Return Call Results report has been updated to ensure that all rows report calls consistently.

Different rows in the Return Call Results report included different FinalFates, which could cause the sum of calls in a column to differ from the value in the Total row. We have updated the report to ensure that all rows include the same FinalFates.

(OPC-1236) Data on the Smart Rules Activity History page can once again be exported to a CSV file.

Previously, attempting to export Smart Rules history would result in an internal server error, causing the export to fail.

(OPC-1306) An issue that could cause the RabbitMQ user not to be added during manual installation has been resolved.

In some cases, a manual installation of RabbitMQ could fail to add the RabbitMQ user to the required configuration, causing the service not to start. An update in this release will ensure that the user is always configured.