Version 84.23.0.123 (V24.3-GA)

Release date: July 20, 2026
Release version: V24.3-GA
Previous version: Version 84.23.0.24 (V24.1-GA)

Overview

Version 84.23.0.123 moves the Virtual-Call Cloud PBX from beta to General Availability. This release focuses on the new call quality monitoring capability, expanded AI receptionist functionality with custom tools, and a range of improvements to call reports, integrations, and extension management.

New Features

Call Quality Monitoring

The Cloud PBX now monitors call quality for extensions in real time during calls and provides detailed performance reports, helping you diagnose and resolve call issues faster.

The following related updates were also introduced:

• A new event notification, Poor Call Quality Reminder (path: System > Event Notification > Event Type > Reminder), is triggered when a monitored call is rated as having poor overall call quality.
• Extended API interfaces for extensions (query/configure call quality monitoring) and for call reports (additional metrics for endpoint, network, score, and quality details).

Enable Call Quality Monitoring

To use call quality monitoring for an extension, follow these steps:

Prerequisites

• The Cloud PBX is running version 84.23.0.123 or later.
• The following minimum versions apply for the Virtual-Call UC Client:
  • Mobile Client: version 5.27.18 (iOS) / 5.27.12 (Android) or later
  • Desktop Client and Web Client: no client update required — the feature becomes available automatically once the Cloud PBX is updated.

Step-by-Step Configuration

1. Log in to the Virtual-Call Cloud PBX admin portal and go to Extension and Trunk > Extension.
2. Click Edit next to the desired extension.
3. Under the Features tab, configure the following:
   • Select the Monitor Call Quality checkbox.
   • In the Monitoring End Time drop-down list, specify when monitoring should end (up to 7 days).
4. Click Save and Apply.

Result

Once the extension is on a call, quality data is automatically collected. This generates a per-call report as well as an aggregated report at the extension level:

• View the per-call report: path Reports and Recordings > CDR > CDR (Advanced) > CDR Details.
• View the aggregated report: path Reports and Recordings > Call Reports > Default Reports > Quality of Service Report (see below).

Extension users can also view the per-call report directly from their Virtual-Call UC Client (Mobile, Desktop, or Web Client, under call logs).

Quality of Service Report

The new Quality of Service Report provides an overall assessment of call quality and detailed insights into individual calls — including breakdowns by client type and network type, with metrics such as MOS score, packet loss rate, jitter, and latency.

Access the report via Reports and Recordings > Call Reports > Default Reports > Quality of Service Report. You can filter the report by extension, extension group, organization, communication type, client type, network type, or overall score, and save it as a scheduled report for recurring delivery.

AI Receptionist – Custom Tools

The AI receptionist can now be equipped with custom tools based on HTTP requests. Once assigned, the AI receptionist automatically invokes these tools during a call to retrieve information or perform actions in external systems (for example, checking an order status or booking an appointment).

The call detail record (CDR) for AI receptionist calls has also been enhanced: every tool call made by the AI receptionist during a call is now logged, including the tool name, execution status, and the full request parameters and response results.

Improvements and Bug Fixes

Web Interface

Added support for two new web interface languages: Catalan and Hungarian.

Extension Group

Fixed an issue where the member list appeared empty and querying the extension group via API returned no data if an extension's first or last name was set to blank via API.

Auto Provisioning

• Added support for retrieving configuration files via HTTP to auto-provision Cisco SPA series IP phones.
• Fixed an issue where, after bulk-adding Yealink IP phones with the random phone password option enabled, the system failed to generate a password for the first phone.

Inbound Route

Fixed the following display issues in the inbound route list:

• When a default destination was set and time-based routing was then configured before saving, the route worked correctly but did not appear in the list.
• After switching a custom-time-period-based route to AI Receptionist via feature code, the Current Destination column showed blank instead of the AI receptionist.

Call Flow Designer

Fixed an issue where, if a trunk's DID number was assigned to a call flow, changing the trunk settings (other than the DID number) caused the DID number to disappear from the call flow list, and calls to that number were no longer routed to the call flow.

Voicemail

Added a No Greeting option for voicemail greetings. When selected, the system does not play a greeting before callers leave a voicemail message. Available for:

• Extension voicemail greeting (path: Extension and Trunk > Extension > Voicemail > Voicemail Greeting)
• Group voicemail greeting (path: Call Features > Voicemail > Group Voicemail > Group Voicemail Greeting)
• Global voicemail greeting (path: Call Features > Voicemail > Voicemail Settings > Greeting Options > Global Voicemail Greeting)

AI Transcription

Fixed an issue where usage was tracked in seconds but incorrectly displayed in minutes, making reported usage appear significantly higher than actual usage.

Message Channel

Updated the authentication method for the Bandwidth SMS channel integration to match the provider's updated requirements: the integration now uses a client ID and client secret instead of a username and password.

Hot Desking

Fixed an issue where, after a bulk update of voicemail access PINs, extension users could not log in to hot desking phones with the updated PINs.

Microsoft Entra ID (Azure Active Directory) Integration

• Fixed an issue where, when the user range for automatic extension creation was set to specific groups, newly added users in the specified Microsoft Entra ID group(s) were synced to the extension list but not added to the corresponding extension group(s) synced from Microsoft Entra ID.
• Fixed an issue where syncing users with a blank email address from Microsoft Entra ID cleared the email field on the corresponding extensions, which unexpectedly signed those users out of their Virtual-Call UC Client.
• Fixed an issue where enabling Microsoft Teams presence synchronization for more than 200 extensions in bulk caused CPU load to reach 100%.

CRM/Helpdesk Integration Templates

• Added support for saving a default template as a custom template.
• Added support for editing a custom template's XML content directly in the view window.
• Enhanced custom template configuration options:
  • Connection Keepalive: sends keep-alive requests to the CRM/helpdesk system at a configurable interval to monitor connection status and authentication validity, preventing the connection from closing due to network timeout or inactivity.
  • Authentication Method: when configuring OAuth2 authentication, you can now add up to 10 custom fields and mark each as required or optional.
  • Call Journal: new settings let you specify the request method (POST or PUT) for creating and updating call log entries.

Call Detail Records (CDR)

• Improved CDR list filters: added column filters for Source Trunk, Destination Trunk, and DID/DDI; moved the Outbound Caller ID and PIN Code filters from the top filter bar into column filters.
• Fixed an issue where monitoring time was incorrectly included in the pure talk duration calculation for monitored calls.

Recording File

Fixed an issue where archived recordings of inbound calls to queues or ring groups could not be played or downloaded.

Call Report

Improved the extension call statistics report: for a monitored call, the report now shows two separate entries with metrics for the monitored party and the monitoring party.

API

• Added new CDR API interfaces (v2.0) for querying CDR data and configuring CDR options. Note: these interfaces can only retrieve CDRs generated on version 84.21.0.117 or later.
• Improved the call transfer report API event to include the destination extension number for blind transfers.
• Fixed an issue where a Redis exception caused the system to return a "TOKEN EXPIRED" error even when the token was still valid.

Best Practices

• Update your Virtual-Call UC Client to the latest version before using call quality monitoring, to get the full set of call quality metrics.
• If you use the Bandwidth SMS integration, update its authentication to OAuth 2.0 well ahead of December 2, 2026 to avoid service interruption.
• Roll out new AI receptionist custom tools gradually, and test each integration in a staging environment first.