Firmware 84.23.0.123-beta1 Release Notes

This is the first beta build (beta1) of Cloud Voice firmware 84.23.0.123. It introduces Call Quality Monitoring, extends the AI Receptionist with custom HTTP tools, and delivers a round of improvements and fixes spanning provisioning, voicemail, messaging, identity and CRM (customer relationship management) integrations, call detail records (CDRs), and the API.

• Release date: June 29, 2026
• Release version: V24.3-Beta (firmware 84.23.0.123)
• Base version: 84.23.0.83

Note

This is a beta release. To try the new features, open your PBX admin portal, check for a firmware update, and upgrade your phone system.

New features

Call quality monitoring

Cloud Voice can now track the quality of an extension’s calls in real time while they are in progress and generate call performance reports with detailed metrics. This gives your technical support team the data it needs to pinpoint and resolve call problems more quickly.

The feature ships with the following related updates:

• A new Poor Call Quality Reminder event notification (System > Event Notification > Event Type > Reminder) fires whenever a monitored call is rated as having poor overall quality.
• The API was extended to support the feature:
  • Extension: enb_monitor_call_quality and monitoring_end_timestamp were added to extension/get, extension/query, extension/create, and extension/update, so you can query or set call quality monitoring on an extension.
  • Call report: endpoint, network, call_score, cdr_id, and qos_call_quality_list were added to call_report/list, call_report/detail, and call_report/download, so you can read call quality details from within call reports.

AI receptionist

You can now build a set of custom tools on top of HTTP requests and assign them to an AI receptionist. Once assigned, the receptionist decides for itself when to call each tool as the conversation unfolds, for example, to check an order status or book an appointment, reaching out to external systems mid-call to retrieve information or complete an action.

The feature ships with the following related updates:

• Custom tools can be assigned to an AI receptionist for more flexible conversation handling.

  

• CDRs for AI receptionist calls were expanded. Every tool call the receptionist makes during a call is now recorded in the CDR detail, including the tool name, its execution status, and the full request parameters and response.

  

Improvements and bug fixes

Web interface

Added two web interface languages: Catalan and Hungarian.

Extension group

Fixed a member list issue: when an extension’s first or last name was set to null through the API, the member list of the extension group it belonged to appeared empty, and querying that extension group through the API returned no data.

Auto provisioning

• Cisco SPA-series IP phones can now be auto-provisioned by retrieving their configuration files over HTTP.

  

• Fixed a random password issue: after bulk-adding Yealink IP phones with Generate a random phone password enabled, the system did not create the Var Phone Password and User Phone Password for the first phone.

Inbound route

Fixed two display problems in the inbound route list:

• When you created an inbound route, set a default destination, and then configured Time Condition routing before saving, the route worked but did not show up in the list.
• After an inbound route based on Custom Time Periods had its destination switched to an AI Receptionist through a feature code, the route’s Current Destination column showed empty instead of the AI receptionist.

Call flow designer

Fixed a DID number issue. A DID (Direct Inward Dialing) number is a specific external number that routes an outside call straight to an internal destination. When a trunk’s DID number was assigned to a call flow, changing any other trunk setting 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

A No Greeting option was added for voicemail greetings. When it is selected, the system plays no greeting before a caller records a message. The option is available in three places:

• Extension voicemail greeting (Extension and Trunk > Extension > Edit > Voicemail > Voicemail Greeting)

  

• Group voicemail greeting (Call Features > Voicemail > Group Voicemail > Edit > Group Voicemail Greeting)

  

• Global voicemail greeting (Call Features > Voicemail > Voicemail Settings > Greeting Options > Global Voicemail Greeting)

  

AI transcription

Fixed a usage display error: usage was measured in seconds but shown in minutes, so the reported figure was far higher than actual usage.

Message channel

The Bandwidth SMS channel integration now authenticates with a Client ID and Client Secret instead of a Username and Password, in line with Bandwidth’s updated authentication requirements.

Caution

If you already have a Bandwidth integration, update it before December 2, 2026 to avoid a service interruption. On the channel’s authentication page (Messaging > Message Channel > Edit > Authentication), click Update Authentication and enter the new OAuth 2.0 credentials generated in your Bandwidth account. You do not need to disconnect and rebuild the integration.

Hot desking

Fixed a login issue: after voicemail access PINs were bulk-updated for extensions, users could not sign in to hot desking phones with the new PINs.

SIP settings

A TLS V1.3 option was added to the TLS Connection Method setting (PBX Settings > SIP Settings > TLS > TLS Connection Method). TLS (Transport Layer Security) is the encryption layer that protects SIP (Session Initiation Protocol, the signaling that sets up and tears down calls) traffic. When it is selected, the system uses TLS 1.3 to establish outbound SIP client connections, for stronger security.

Caution

TLS 1.3 also has to be supported by the device or provider at the other end of the connection. If the far end does not support it, the outbound SIP connection will fail to establish, which can stop calls from going through. Confirm both ends support TLS 1.3 before changing this on a live trunk.

Microsoft Entra ID (Azure Active Directory) integration

Fixed several user synchronization problems:

• With User Range for Extension Auto Creation set to Users in Specific Group, newly added users in the specified Microsoft Entra ID group(s) synced to the PBX extension list but were not added to the matching extension group(s) synced from Microsoft Entra ID.
• Syncing users that had blank email addresses cleared the email field on the matching PBX extensions, which unexpectedly signed those users out of the Cloud Voice App.
• Enabling Microsoft Teams User Presence Synchronization for more than 200 extensions at once drove CPU load to 100%.

CRM/Helpdesk integration template

• A default template can now be saved as a custom template.

  

• You can edit a custom template’s XML directly in the view window.

  

• Several custom template settings were refined:

  • Connection Keepalive was added to the Request Configuration section. When enabled, the system sends keep-alive requests to the CRM/Helpdesk at a set interval to check the connection status and authentication validity, preventing the connection from dropping after a network timeout or a spell of inactivity.

    

  • The Authentication Method configuration was improved: when you set up OAuth2 authentication on the template page, you can add up to 10 custom fields and mark each one as mandatory with the Required field.

    

  • The Call Journal configuration gained Create Call Log Request Method and Update Call Log Request Method items, letting you set the request method to POST or PUT.

    

CDR

• The filters in the CDR list were reworked.

  

  • New column header filters were added: Source Trunk, Destination Trunk, and DID/DDI (DDI, Direct Dial-In, is the European term for a DID).
  • The Outbound Caller ID and PIN Code filters moved from the top filters to column header filters.

• Fixed a Pure Talk Duration miscalculation: monitoring time was wrongly counted toward Pure Talk Duration on monitored calls.

Recording file

Fixed a playback and download failure: archived recording files from inbound calls to queues or ring groups could not be played or downloaded.

Call report

The Extension Call Statistics report was improved: for a monitored call, it now shows two separate entries, one carrying the metrics for the monitored party and one for the monitoring party.

API

• New CDR interfaces were added under openapi/v2.0 for querying CDRs and setting CDR options.

  Note

  The openapi/v2.0 query interfaces can only retrieve CDRs generated on version 84.21.0.117 or later.

• API event 30013 (Call Transfer Report) now includes the destination extension number when the transfer is a blind transfer.

• Fixed an error-code bug: a Redis exception made the system return error code 10004 (TOKEN EXPIRED) even when the token was still valid.