No audio on incoming calls, outgoing fine.

[MMDTerry]

I am setting up a Chromebox with chrome 81.0.4044.141 installed. login to the web client and set the audio devices to the headset (have tried a jabra pro 9450 and a usb headset) and made a ext to ext outbound test call, worked great. Had a co-worker try a ext to ext inbound call. Rings but zero audio on either side. I have tried with and with out the 3cx chrome extension and it made no difference. Tried on my W10 desktop everything works just as it should. Any one have an issue like this before?

 

[MMDTerry]

Update.

If while on a incoming call I go to setting/personalize/audio/video and change the speaker from the headset to the HDMI output, then back to the headset the headset speaker and mic start working. Not sure if this is a bug in the web-client site or an issue with chrome/chromeOS. hunting down another chromeOS device to test.

 

[mpersak]

Hi

I've got similar issue. At first audio didn't work at all. Firewall test for some reason failed on second part of RTP ports, even though they were open.
I've performed full reinstall - backup restore.
After that firewall test goes through fine, also 3cx chrome plugin works on outbound calls.
There is still no audio on inbound calls - caller can hear himself.
Strangely enough, is I've used a different trunk provider and it works fine in and out, while with our main trunk provider there are issues.
There was never issue on 3cx desktop client, phones behind PBX and also phones registrered from outside using STUN....
looks like chrome plugin works completely differently than any of other options...

 

[MMDTerry]

Web client and plugin give me the same results, phones, mobile apps and external phones work fine. Verified with another chromebook that the issue is isolated to the chromebox. Im guessing its an audio routing issues within the webclient or chrome since i can get it to work by changing the speaker/mic settings to the HDMI i/o then back to headset. All other audio like zoom or the 3cx webmeeting work as they should so im thinking its an issue in the webclient were its ignoring the settings under personalize>audio/video.

 

[MMDTerry]

Used a hp Chromebook to test. internal speakers and mic work great. Plugged in the headset, it functions as it should too. plug in an external display via type-c to HDMI adapter, no audio. made sure all settings in chromeos and the web-client are set to the USB headset and no change.

For sure a audio routing issue, but who is to blame?

 

[MMDTerry]

Well its just the 3cx web client that has issues. YouTube works fine with the external display and headset on two devices but for some reason with chromeOS an incoming call will not route the audio correctly if an external display is attached via HDMI.

Not sure if the 3cx dev's care because im sure its a very small subset of users that are using chromeOS with multiple displays.

off to find a different solution until the Android app is available.