What's in the Update?
7.5 introduces several new features and enhancements.
Call recording transcriptions are now available, which enables customers to have their call recordings automatically transcribed.
The new Event Manager allows you to streamline workflows between the CloudPBX and third-party platforms/services based on predefined system events.
MOS (Mean Opinion Score) has been added to call reports to help users monitor call quality
Additionally, SSO (Single Sign-On) support has been added, allowing users to access multiple applications or services using only one set of login credentials.
These updates provide greater control and flexibility, enhancing the overall CloudPBX experience
Call Recording Transcriptions
Version 7.5 introduces a powerful new feature: Call Recording Transcription, which allows customers to have their call recordings automatically transcribed and linked to their Call Detail Records (CDRs). This enhancement enables users to easily review transcriptions, without having to listen to the whole call recording.
Transcriptions for recorded calls will be accessible from the CDR Reports page.
To view a transcription, users can simply select the desired CDR and click the transcription button located in the top left corner.
The corresponding text for that recording will appear on the right-hand side
Users will also have the option to view subtitles of call recordings while playing them directly within the CloudPBX interface, if there is a transcription available
Note: If MP3 Auto Conversion is disabled, transcriptions will still be available, but subtitles will not be displayed.
This is because direct playback of recordings within the CloudPBX GUI requires MP3 conversion to be enabled.
This feature can be configured within a newly added section in Server Settings called Call Recording Transcription.
Customers can select their preferred transcription provider from the available options.
We are pleased to announce that OpenAI and Hosted Whisper are currently supported as transcription providers.
Single Sign-On
Single Sign-On (SSO) is an authentication process that allows users to access multiple applications or services using only one set of login credentials.
The primary goal of SSO is to simplify the user experience by reducing the number of times a user has to log in when accessing different systems or services.
In a traditional authentication setup, each application or service requires its own set of credentials, leading to multiple login processes and the need to remember multiple usernames and passwords. SSO addresses this challenge by enabling users to log in once and access various systems or services without re-entering their credentials for each service individually.
To improve the user experience for our customers, we are glad to introduce CloudPBX Single Sign-On compatibility with Google and Microsoft services
Communicator App for Microsoft Teams
With the release of Version 7.5, you can now create a custom Communicator App tailored specifically for your customers' Microsoft Teams environments. (There may be some additional charges, depending on the final setup).
These apps can be deployed either on a per-customer basis or individually for each of your CloudPBX instances, offering flexibility in how you deliver the solution.
The key advantage of this update is that it enables your customers to access and use the functionality of the Communicator application directly within Microsoft Teams - without the need for a Microsoft Teams Phone System licence.
This presents a cost-effective and seamless integration path for customers who want unified communication capabilities within Teams but don’t require the full Microsoft calling add-on.
This new feature enhances user experience, simplifies deployment, and opens up broader adoption opportunities by reducing licensing overhead.
Let us know if you'd like assistance setting this up or showcasing it to your clients.
Microsoft Teams Presence Integration
Version 7.5 introduces the ability to synchronize Microsoft Teams’ presence status with the Communicator client application (Desktop, Webapp, and Mobile) extension’s presence.
For more information see the full guide on configuring Teams Presence Integration
Before this integration can be enabled, it is necessary to create the required OAuth apps and credentials (which can be found and created in
Settings -> OAuth on the desired tenant)
After Oauth apps and credentials have been configured, the Microsoft Teams Integration can be enabled by setting the Enable Presence Sync option to “Yes”, which can be found in the Settings -> Microsoft Teams -> Settings tab.
The Teams Presence Sync option can also be customized at the extension level.
This can be adjusted by opening an extension’s settings, clicking the “Show Advanced Options” button, and scrolling to the Communicator section, where the Teams Presence Sync can be turned on or off.
When the Teams Presence Sync option does not have the same value at the tenant and extension levels, the extension setting takes precedence:
• If the Teams Presence Sync option is set to “Yes” at the extension level, the same option will be overridden at the tenant level. Teams Presence Sync is turned on.
• If the Teams Presence Sync option is set to “No” at the extension level, the same option will be overridden at the tenant level. Teams Presence Sync is turned off.
• If the Teams Presence Sync option is set to “Not Set” at the extension level, it will only be turned on if the same option is set to “Yes” at the tenant level.
Microsoft 365 Contacts
The release of Version 7.5 introduces the Contacts feature, which enables seamless integration with external contact sources such as Microsoft 365 and Custom Contact Sources.
Administrators can easily synchronize external directories into the CloudPBX, making contact data available across the system without needing to manage contacts manually.
This includes full support for initial full syncs and incremental updates — meaning only newly added, modified, or deleted contacts are synced after the initial connection.
Configuration is available directly through the Contacts -> Settings page in the CloudPBX interface, where users can define sync intervals, trigger manual syncs, and monitor sync status.
Syncing can be performed either automatically on a set schedule or manually using the Trigger Sync option.
These Contact will show in the UC Applications, just like the Central Phonebook Contacts.
For more information see the full guide on configuring Microsoft 365 Contacts
Event Manager
The addition of the Event Manager opens up a whole new world of possibilities for CloudPBX administrators by providing the ability to streamline workflows between the CloudPBX and third party platforms/services on predefined system Events like:
• Incoming Call
• Answered Call
• Unanswered Call
• Hangup
• Ringing
Actions allow you to create custom HTTP requests which can be enriched by defining queries, body and headers, authorization of HTTP requests, and with system and custom parameters using tags, which are defined in the Parameters section.
Parameters are replaced with relevant data on each request.
Once the system triggers an active Event, all HTTP requests that are attached as Actions are sent. This section displays the system’s default (predefined parameters) and custom parameters that the admin can create and use inside the Actions themselves.
Note: Default parameters cannot be deleted or edited, and they can be found in the parameters list with a cog icon before the parameter’s name.
On Multi-tenant systems, Actions can be imported from the master tenant, from a Postman Collection, and can also be added manually.
In addition, the HTTP request sending history, including response data sent by the system, can be checked in the Activity Monitor in the Events section.
Note: Event Manager needs configured for each tenant individually.
For more information see the full guide on configuring Event Manager
Mean Opinion Score (MOS)
In Version 7.5, call reports now include a new metric: MOS (Mean Opinion Score), allowing users to monitor call quality.
This metric has been added as a column on the CDR Reports page, where call quality is displayed for each individual record.
The value displayed represents the average score across all channels within the call that share the same linked ID.
Additionally, clicking the MOS score will open a pop-up which shows detailed information about call quality, enabling users to analyze each channel individually by viewing its minimum, average, and maximum MOS scores.
NEW PROVISIONABLE END POINTS