SangomaTalk Visual Voicemail not play audio message

We recently setup a FreePBX 17 and purchased the 20pack SangomaConnect for Mobile phones.

As of title, the visual voicemail is not working: it show the messages, allow to delete, but not play audio. The dots just spin forever.

Dialing the voicemail everything is fine.

Our FreePBX is in a dedicated VLAN so from LAN there is a router/firewall that control the access and from Internet there is also NAT that can cause issue. I can’t find any documentation of what is needed, if anything is needed, to make things work.

Any help appreciated.

Here’s a guide to Ports used on your PBX but that said, have you tried a different browser ?

Thanks for reply. I’ll check again the ports.
But the issue happens on Android/iOS SangomaConnect for Mobile app, no browser involved.

Hi @unlikely Please refer to the https://sangomakb.atlassian.net/wiki/spaces/SS1/pages/30966602/SC_Apps-+Visual+Voicemail+App wiki and F&Q section(at the end of the wiki) to ensure you have proper configuration in place.

Some small progress… Now the tap on play show a scroll bar for a zero lenght audio, still listening nothing. What’s the next step?

Compare the behavior with the ucp voicemail widget or list of voicemails ucp is showing is same as talk visual voicemail or not, does ucp voicemail widget works fine for you ?

If you are not able to make progress then I would suggest you to raise commercial module support ticket so any of our support team member can help you out to solve your issue.

Thanks

The UCP voicemail widget works fine both from the LAN and from outside.

The Sangoma Talk Visual Voicemail doesn’t play any audio.

does 159.203.120.54 whitelisted in your PBX/Firewall?

Hello, what is this ip?

What do you means exactly by “whitelisted”?
What protocol and port should be NATted to FreePBX through firewall for this source ip?

Please check below section.
https://sangomakb.atlassian.net/wiki/spaces/SS1/pages/30966602/SC_Apps-+Visual+Voicemail+App#F&Q

This IP is our server which is executing Voicemail Webview so this ip should be whitelisted in the firewall of PBX or external firewall if configured in front of PBX in order to fetch/play the audio file from the PBX.

Ok but what do you means by “whitelisted”?
What exact service/protocol/port should this ip be allowed to access on freepbx instance?
Could be already “whitelisted”…

Allow your PBX to accept/process HTTPS request from 159.203.120.54 IP.

https on tcp/443 port?
This should be enabled from every public ip.
The request is processed by a reverse proxy and “forwarded” to freepbx.

Not sure if related, but “Visual Voicemail app” is working now from Sangoma P330 Phone.
But still not working from Sangoma Talk Android App.

Connectivity Flow for the Sangoma Talk Webview App (Voicemail)

SangomaTalk ==>scproxyapps.api.apps.sangoma.com(159.203.120.54:443) =>PBX:sslsngphone(6443)

Ensure that the IP address 159.203.120.54 can access the sslsngphone port (6443) of your PBX.

I changed the port of Sangoma Connect to 8443 for the reasons already explained.

Typing https://pbx.mydomain.tld:8443 in a browser returm me a forbidden page with no https warning, so the web server is reachable from everywhere. I can see an entry in the access log of my reverse proxy.

But I can’t see any hit to pbx.mydomain.tld:8443 in the access log of my reverse proxy when opening Visual Voicemail from Sangoma Talk Android App and any access attempt from 159.203.120.54.

Are you sure the sslsngphone service is listening on port 8443? You can confirm it using the following command:

root@uc-:~# fwconsole sa ports
+------+-------------+-------------+
| Port | Name        | Force https |
+------+-------------+-------------+
| 82   | restapps    | Disabled    |
| 83   | restapi     | Disabled    |
| 81   | ucp         | Disabled    |
| 2001 | acp         | Disabled    |
| 84   | hpro        | Disabled    |
| 80   | leport      |             |
| 3443 | sslrestapps |             |
| 2443 | sslrestapi  |             |
| 4443 | sslucp      |             |
| 443  | sslacp      |             |
| 1443 | sslhpro     |             |
| 6443 | sslsngphone |             |
+------+-------------+-------------+

After verifying, you can run the tcpdump command with that port to check if it is receiving traffic on your PBX:

tcpdump -i any "port <sslsngphone>"

Thanks for reply. Port 8443 is listening for sslsngphone service.

+----------+-------------+-------------+
| Port     | Name        | Force https |
+----------+-------------+-------------+
| disabled | restapps    | Disabled    |
| disabled | restapi     | Disabled    |
| disabled | ucp         | Disabled    |
| 80       | acp         | Disabled    |
| disabled | hpro        | Disabled    |
| disabled | leport      |             |
| 2087     | sslrestapps |             |
| 2443     | sslrestapi  |             |
| 2053     | sslucp      |             |
| 443      | sslacp      |             |
| 2096     | sslhpro     |             |
| 8443     | sslsngphone |             |
+----------+-------------+-------------+

As already written when I visit https://pbx.mydomain.tld:8443/ with a browser or curl I get a response from freebx (403 Forbidden) and reverse proxy log the access and tcpdump show traffic, no matters of the network (LAN, VPN, WAN).

But when I open Visual Voicemail in Sangoma Talk Android app nothing happens in the logs.

I can also add: apparently my android phone never attemt to connect to 159.203.120.54.

What if you change from your custom 8443 to the default 6443 ? (From Eight to Six)

And then update your external firewall accordingly to forward from only:

…to your PBX at 6443.

I can’t.
6443 is not forwarded by cloudflare proxy.
It would be nice and a lot easier for firewall/proxy if all http(s) services of freepbx were accessible under only 80/443 ports, maybe under different path and/or different hostname/SNI…