Embedded Files
What's in the Update?
CloudPBX v7.6.0 introduces several new features and enhancements.
Call forwarding based on Communicator presence
Single Sign-On (SSO) generic OpenID Connect (OIDC) provider integration
Opt-Out, Opt-In and help keywords for SMS messaging
AI Voice greeting generation (text to speech)
OpenAI for voicemail transcription
Call Recording transcription support for longer calls
Stereo call recordings (beta)
Event manager added OAuth 2.0 support
Disable SMS message and conversation deletion
New endpoints
Call Forwarding Rules Based on Communicator Presence
Destinations for call forwarding based on the app presence status can now be configured within the Enhanced Services page of an extension, under Call Forwarding settings.
To preserve the existing call forwarding functionality, the Call Forwarding section is now divided into two tabs: Standard and App Presence. The Standard tab contains all previously available forwarding options, while the App Presence tab introduces new settings that allow call forwarding based on app presence statuses.
Within the App Presence tab, administrators can define forwarding destinations for default app statuses - Busy, Do Not Disturb, and Away - as well as any custom presence statuses created under Apps > Statuses. When an extension is online and logged into any Communicator client, and its presence changes from Available to a status that has call forwarding rules configured, those rules will be applied automatically.
For each presence status, up to 10 forwarding destinations can be set for both local and external calls.
A new option, Prioritise Call Forwarding based on App Presence, has been added to control the precedence of forwarding rules. When set to Yes, App Presence rules will take priority over standard forwarding rules. The system will first check if the current app presence matches any configured rules; if a match is found, those rules will be applied immediately. If not, standard rules will apply. The default value for this setting is No, which means standard rules are prioritized by default.
Additionally, extensions with the Allow in OSC permission can manage their own call forwarding rules - for both the Standard and App Presence tabs - directly via OSC.
SSO: Generic OpenID Connect (OIDC) Provider
Integration with CloudPBX
In ClodPBX 7.6.0, a new option has been introduced which allows administrators to easily configure and enable additional Single Sign-On (SSO) providers through the Settings > Single Sign-On > Providers page, where all available SSO providers are listed.
Clicking the “Add new provider” button opens a setup page intended for configuring the new SSO option.
On the configuration page, administrators can:
Enable or disable the provider using the “Enable” field by setting it to “Yes” or “No”
Enter a “Label” for the provider, which will appear on the login page
Provide the “Client ID” and “Client Secret” obtained from the provider’s application.
Copy the generated “Callback URI”, which is automatically created based on the server settings and can be used in the provider’s application.
Fill out the “Auto Discovery URI” using the placeholder as a template, depending on the provider that is being configured.
Upload an SVG logo to display on the CloudPBX login page for this SSO option by clicking the “Upload SVG Logo” button.
Note: Some providers do not support the ./well-known/openid-configuration endpoint and cannot be configured.
Custom providers can be edited and deleted, while the default Google and Microsoft Entra ID providers can only be edited.
Once configured correctly, custom providers will appear as options on the CloudPBX login page
Opt-Out/In and Help Keywords for Non-Bulk Messaging
In CloudPBX 7.6.0, support for Opt-out, Opt-in, and Help keywords has been extended to conversational SMS messaging. Previously, these keywords were only available for use in bulk messaging. With this update, they can now also be used in one-on-one (conversational) SMS messaging at any time during a direct SMS conversation.
On the SMS Settings > Options page, a new drop-down menu called Opt-Out Scope has been added, which will be applied to both Bulk messaging and conversational SMS messaging. This setting controls how the system handles Opt-Out requests from recipients who reply to SMS messages using predefined Opt-Out keywords. It determines whether the Opt-Out action will apply to a specific From Number or to all SMS numbers associated with the tenant.
You can choose between the following two options:
Global
When set to Global, replying with an Opt-Out keyword will block the recipient’s number from receiving SMS messages from all SMS numbers on the tenant. The number will be added to the Blocklist with the “From Number” set to ALL.
SMS Number
When set to SMS Number, the Opt-Out action will only block messages from the specific SMS number the recipient replied to. The number will be added to the Blocklist with the “From Number” set to the number that received the Opt-Out message. The recipient can still receive messages from other SMS numbers on the tenant.
Additionally, an option to edit blocked numbers has been added to the SMS > Blocklist page Administrators can now modify existing numbers by selecting a number from the new drop-down menu, From Number. This allows them to specify whether the blocked recipient should be prevented from receiving messages from a specific SMS number, multiple numbers, or all SMS numbers on the tenant.
AI Voice Greeting Generation (Text to Speech)
With this release, administrators can generate AI voice recordings from text using the OpenAI Text to Speech API. These recordings can be assigned to IVRs, ring groups, voicemails, and more. The feature is available through the “Generate sound file” button under System > Sound files. Clicking the button opens a pop-up where the administrator can enter details for the sound file they want to create.
Users will be prompted to select a Model and the specific voice they wish to use, which can be previewed instantly by clicking the “Play sample” button. This enables administrators to tailor the sound file to their exact needs.
When generating the file, users can also specify its intended purpose so the system can automatically create an appropriate file name.
Within this pop-up, there is a text section where administrators can type out the greeting or message that they want to be played. Before saving, they can listen to the generated audio and make adjustments as needed until they are satisfied with the final result.
Note: for any new changes, users have to click “Generate” again in order for the changes to apply. After pressing “Save”, the file will be saved and available to use within the sound files.
OpenAI for Voicemail Transcription
With this new release, OpenAI can now be used as a provider for voicemail transcriptions. When selected, users will be prompted to enter their API key, choose the language, and provide a prompt.
The voicemail transcription feature continues to function as before: if ‘Enable Service’ is set to ‘No’ or ‘Not Set’, voice messages will not be transcribed.
Call Recording Transcription Support for Longer Calls
To improve transcription accuracy for longer calls or recordings that exceed provider file size limits, audio chunking has been added. The system now automatically detects when a recording exceeds the limit that a provider can handle and splits the audio into smaller, appropriately sized chunks, enabling complete and accurate transcription even for extended calls.
Stereo Call Recordings (Beta)
A new hidden option has been introduced to enable stereo call recordings, allowing each side of the conversation to be recorded on a separate audio channel, which unlocks several benefits, such as Improved AI readiness, enabling advanced tools for speech analytics, speaker diarization, and transcription; and Better integration with AI, CRM, and analytics systems. These recordings follow the same retention and deletion policies as standard (mono) recordings. The feature can be enabled either globally (for all tenants) or individually per tenant. As this functionality is still in the beta state, it remains a hidden option for now. To have this option enabled, please contact our customer support.
Note: If stereo call recordings have been enabled, RAMFS should be increased to at least 256 MB since stereo recordings are much larger in file size than mono recordings. The final MP3 recordings are typically 2-3 times larger than mono recordings.
Event Manager: Added OAuth 2.0 Support
Event Manager now supports OAuth 2.0 as an authentication method for outgoing webhook actions. When this option is selected, CloudPBX automatically obtains an access token by using the configured Token URI, Client ID, and Client Secret, and includes the token in the request header. This enables secure integration with third-party APIs that require dynamic token-based authentication. The token is automatically refreshed when it expires, reducing the need for manual handling. This new method complements the existing authentication options: No Auth, API Key, Basic, and Bearer Token. With this enhancement, the Event Manager becomes more adaptable and secure for modern automation workflows.
Disable SMS Messages and Conversation Deletion
For security reasons, a new setting allows administrators to prevent users from deleting SMS/MMS messages or conversations in Communicator. The option can be found in the Communicator > Settings page, where SMS/MMS message and conversation deletion from Communicator apps can be controlled by selecting either “Yes”, “No” or “Not Set” for the new “Disable SMS/MMS Deletion” setting. This option can be set at both the master and tenant levels, where the tenant level takes precedence over the master tenant.
NEW PROVISIONABLE END POINTS
Report abuse