webclient no sound

[Fishball0206]

i facing problem about call out is no voice using chrome webclient.
Use 3cx desktop version and 3cx softphone app no issue.
only use webclient call out and call in cannot listen sound.

 

[JohnS_3CX]

Hi,

In order for the webclient to work, your PBX must have all the necessary ports forwarded otherwise it will not have audio https://www.3cx.com/docs/ports/

You can start by running the firewall checker in your 3CX Management console


Then you can look here to see the necessary ports to open on your firewall if the test failed
https://www.3cx.com/docs/ports/

And of course, make sure that you go to your Webclient Settings > Personalize > Audio/Video and ensure the correct audio devices are selected. The site settings must allow the webclient site to access to your microphone too. Click the Lock icon in Chrome and allow if you haven't already otherwise you will see an error telling you it cannot access your media devices:

 

[Absoblogginlutely]

We've had this reported with the latest Edge Beta ( Version 85.0.564.36 (Official build) beta (64-bit) and the 4.3.0319 extension where there is no outgoing sound. Can hear people calling in, but they can't hear us.
No issues with the non dev version of Edge or the Chrome plugin.
Reproduced on multiple devices. The fact that it works for other browsers implies it is not a firewall issue.

 

[JohnS_3CX]

It could still be a firewall issue, the other 3CX softphones use the tunnel port to pass audio, whereas the Webclient uses the RTP ports that show up in the firewall checker and in ports document.

 

[DanMac01]

We confirmed this on multiple machines with the version 86 Dev build of Edge Chrome. Multiple network connections.

 

[JohnS_3CX]

@DanMac01 yes, we also see similar issues from time to time with dev/beta builds of Chrome or Edge

So long as the stable builds work fine there is no cause for alarm.

Please use the stable builds for best compatibility.

 

[Workbooster_GmbH]

Have you updated to the latest stable 3CX Version? There was a SSL Issue or something like that.