Cloud Voice 84.22.0.139 (V23.3)

This page records the changes delivered in Cloud Voice firmware 84.22.0.139, covering the build from its beta stages through to the final General Availability (GA) release. GA means the build has finished testing and is considered ready for production use.

To move an existing system to this build:

1. Sign in to the admin portal of your phone system (the PBX, or Private Branch Exchange, is the software that routes your calls).
2. Open the firmware update screen and check for available updates.
3. Apply the update to upgrade your phone system to 84.22.0.139.

Note

“Base version” below tells you the build this release was built on top of. If your system is already running the base version, this upgrade is a small, incremental step rather than a large jump.

Caution

A firmware upgrade restarts the phone system, which briefly interrupts service and drops any calls in progress. Schedule the upgrade during a maintenance window or a low-traffic period.

Firmware 84.22.0.139

• Release date: April 21, 2026
• Release version: V23.3-GA
• Base version: 84.22.0.138

Caution

If your systems are managed from a self-hosted centralized management platform, that platform will not detect this firmware version until its servers are upgraded first. The cluster server must be on version X.19.0.11, and the centralized management server must be on version 87.19.0.27 or later. Upgrade those servers before you try to roll out 84.22.0.139 from the platform.

Bug fixes

Call reports: Corrected an issue where, after upgrading to version 84.22.0.138, the Agent Login Activity, Agent Pause Activity, and Agent Missed Call Activity reports returned no data. These call-center reports now return results as expected.

Related release notes

New features and improvements for the Cloud Voice App (the desktop, mobile, and browser-extension clients your users install) are tracked separately. Check the Cloud Voice App release notes for those details.

Reporting problems

If something does not work as expected on this build, report it through your usual support channel so it can be investigated.