The windows version has no problems but the web version after entering the correct user and password for the enabled user either gives an error or Lost connection to PBX. Reloading…
is there any other port that needs to be opened on the firewall in addition to those needed for Sangoma connect desktop?
A new Voicemail Forwarding feature has been added to the Desktop Softphone Client, allowing users to forward voicemails directly to their coworkers with just a few clicks.
The desktop client codebase has been updated to enable native browser support. Users can now access the Desktop Softphone Client directly via a web browser at Sangoma Phone , without needing to install a standalone application.
Fixed an issue where Caller ID names longer than 20 characters were being truncated. The Desktop Client now properly displays full-length Caller ID names, ensuring better visibility and caller identification.
Fixed an issue where the outbound call ringback tone was playing through the ringer device instead of the selected speaker. The ringback tone now correctly plays through the user’s chosen audio output device.
Thanks for checking out the browser version of the desktop client.
To ensure compatibility, please make sure your PBXact/FreePBX system is updated to the following module versions (or newer):
Sysadmin: v17.0.2.32 or v16.0.49.12
Sangomartapi: v17.0.9.18 or v16.0.54.18
Restapps: v17.0.1.39 or v16.0.36.26
Sangomaconnect: v17.0.3.25 or v16.0.51.22
Once the modules are updated, you can generate the new compatible HAProxy configuration by running the following command:
fwconsole sa rebuildhaproxy
Then, restart the HAProxy service to apply the changes:
haproxy-ctl restart
Important: Restarting HAProxy will temporarily drop all active connections from the desktop client app. However, users will be automatically reconnected and logged in once the service restarts.
If You Encounter Client Reloading / Self-Signed Certificate Warning / WSS Connection Issue:
Browsers may block secure WebSocket (WSS) connections when using self-signed SSL certificates due to security restrictions. Here’s how to manually allow the connection:
Steps to Resolve:
Open a new browser tab.
Enter the PBX IP address or hostname using https. Example: https://mypbx.local
Click on Advanced.
Click Proceed to the site (unsafe).
Once the connection is established, return to https://phone.sangoma.com/ and try logging in again.
We’re in the process of publishing all the necessary prerequisites and instructions in the wiki soon. In the meantime, please follow the above steps to try the browser version, and feel free to share any feedback!
FreePBX version 15 is currently listed on the versions calendar as Security Fix and Commercial Improvements Only with expected End Of Life in less than sixty days.
Sangoma Phone , without needing to install a standalone application.