Chrome Extension on Mac - Cannot see Browser Extension under devices

[Jason Ward]

Hi,

Our users with Macs cannot see the Browser Extension when selecting their phone devices.The extension seems to load ok, and the webclient asks them to enable it etc. If they try and make a call from the extension it just uses any other phone device they have associated.

Have tried both Chrome and the Edge Beta, same results.

Working fine on Windows based machines.

Anyone have any ideas?

Thanks in advance,

Jason

 

[Evolute IT]

Hi,

Our users with Macs cannot see the Browser Extension when selecting their phone devices.The extension seems to load ok, and the webclient asks them to enable it etc. If they try and make a call from the extension it just uses any other phone device they have associated.

Have tried both Chrome and the Edge Beta, same results.

Working fine on Windows based machines.

Anyone have any ideas?

Thanks in advance,

Jason

@JohnS_3CX @StefanW @edossantos @NickD_3CX Any ideas?

 

[Constantinos Constantinou]

Hello @Jason Ward ,

Make sure that you access the Web Client on activation of Chrome Extension with https protocol and NOT http

Let me know if this is the case.

 

[Jason Ward]

Hi,

Looks like that was the problem. Is that requirement highlighted anywhere? Couldnt' find a reference to it.

Jason

 

[Constantinos Constantinou]

Hello @Jason Ward ,

Happy to hear that you manage to address it.

We will try to address it in various ways.

Thank you for your feedback.

 

[JohnS_3CX]

Hi,

Looks like that was the problem. Is that requirement highlighted anywhere? Couldnt' find a reference to it.

Jason

Hi Jason,

For a more technical explanation, this a universal requirement nowadays, regardless of whether you are using local or online services HTTPS is now a must to secure your communications. This includes our webclient as well as anything else that uses WebRTC or the microphone.

You will notice all major browsers like Chrome and Firefox now refuse to serve your http without a stern warning, and they will not allow the user's microphone to be accessed over unsecure connections since 2018 if I remember correctly.