# Cloud Voice 84.23.0.24 This release note tracks firmware 84.23.0.24 across its lifecycle, from the beta build it grew out of to the finalized general-availability version described here. To move your phone system to this release, open the PBX (Private Branch Exchange, your hosted phone system) admin portal, check for a firmware update, and run the upgrade. :::note This page covers only the phone-system firmware. New features and improvements for the Cloud Voice App clients and the Cloud Voice for Google Chrome extension are tracked in their own release notes. If something in this release does not work as expected, report it through your Cloud Voice support channel. ::: :::tip Back up your phone system configuration from the admin portal before you upgrade. If anything goes wrong, you can restore the backup instead of rebuilding settings by hand. ::: :::danger Running a firmware upgrade restarts the phone system. While it reboots, all extensions drop and no calls can be made or received, including emergency (E911) calls. Schedule the upgrade for a maintenance window or off-hours period, and make sure staff have another way to reach emergency services during the restart. ::: ## Firmware 84.23.0.24 - **Release date:** May 14, 2026 - **Release version:** V24.1-GA - **Base version:** 84.23.0.23-beta1 With this build, firmware 84.23.0.24 leaves **Beta** and reaches **General Availability (GA)**, so it is validated and ready to run in production. The GA promotion also brings the following changes. ### Improvements **Extension** An extension's transport protocol is how its SIP (Session Initiation Protocol) call-setup messages travel across the network: UDP (User Datagram Protocol) or TCP (Transmission Control Protocol). This build revises the [extension transport-protocol behavior](/pbx/release-notes/v84-23-0-23-beta1/#v84.23.0.23-beta1__6) first shipped in **84.23.0.23-beta1**. The two builds handle protocols differently: - **Beta1 build:** Upgrading added the **TCP** protocol to every existing extension, and any newly created extension had both **TCP** and **UDP** selected by default. - **GA build:** Those automatic changes no longer apply. Existing extensions keep whatever protocol settings they already had, and new extensions use **UDP** only by default. :::caution The transport protocol allowed on an extension must match the protocol its device or app is set to use. If a phone is configured for TCP but its extension now permits UDP only, the phone cannot register and its calls fail. After upgrading, check any device that was relying on TCP and confirm its extension still allows that protocol. ::: ### Bug fixes **AI Transcription** - Resolved two cases where the AI (Artificial Intelligence) call transcription control was missing from the in-call screen: - When a call was placed from the Cloud Voice App mobile app on a build older than 5.24.13 (iOS) or 5.24.7 (Android). - When a call was answered or placed on a Cloud Voice App client running in CTI mode. :::note CTI (Computer Telephony Integration) mode lets a Cloud Voice App client control a call, such as answer, hold, or transfer, while a separate desk phone carries the audio. ::: **Call Note** - Fixed a case where the call note button was absent even though call notes were enabled on the PBX. It occurred when a user answered a call on a desk phone in CTI mode paired with the Cloud Voice App desktop app. **CDR** - Fixed a CDR export failure: downloading call records as `PDF` or `HTML` did not complete, and the system repeatedly reported that a large task was already running and holding the process. :::note CDR (Call Detail Record) is the log entry the system keeps for each call, covering details such as caller, callee, time, and duration. The admin portal can export these records in several file formats, including `PDF` and `HTML`. :::