Multiple Issues with Chrome Extension since Update 5

[MH_INDUS]

Hello all,

since we updated to v16 U5 and accompanying Chrome Extension we have encountered multiple errors with the Extension.

All Clients are running Windows 10 and Chrome 81

Errors range from:

• WebRTC Line not registered
• This device does not support media settings
• Speakers do not ring when being called
• No Audio when calling

All these errors were resolved by disabling the Chrome extension.

Reinstalling the Chrome extension lead to the next error being encountered.

Are these known issues?

Is there a reliable fix for this, we don't want to disable the extension everywhere?

 

[JohnS_3CX]

Hi,

Check your chrome extension version please, what number do you see?

 

[MH_INDUS]

Hello John,

I just checked the version on my PC and 2 of the affected PC's,

all are running 3.0.1.70

 

[JohnS_3CX]

Do you have any other chrome extensions installed or an antivirus program (other than Windows Defender) or are enforcing any group policies on those pcs?

 

[MH_INDUS]

2 of the PCs have no other extensions beside the dafault google docs extensions and are running Trendmicro AV without the firewall module. I have received no connection blocked/process blocked messages from these computers.

Third pc is not a company pc running at least an adblock extension, not sure about the av on that one.

 

[JohnS_3CX]

1. would it be possible to log in to the webclient from an unrelated pc, the doesnt have a 3rd antivirus, and also disable any other chrome extensions temporarily?

2. Does the firewall checker on the management console pass all the tests when you run it?

 

[MH_INDUS]

Hello Hohn,

I ran the firewallchecker successfully.

Testing on an unrelated pc works without issues, but it also works on almost all company computers, which are identical in regards to OS, Browser, AV and extensions.

So far only 4 people have reported problems with the new extension. But there the issues/errors change after every reinstall of the extension.

 

[JohnS_3CX]

I would recommend to troubleshoot each case individually whenever a user complains because the first problem in the list suggests connectivity issues, and the other 3 suggest either bad audio device configuration, or lack of permissions granted (those errors appear when the extension cannot access audio devices). Your firewall checker passed so there's no reason to suspect audio not being delivered.

Given that what you are reporting is kind of inconsistent, I would like to know if there is a way you can replicate the behavior and would be interested in investigating further with you. Perhaps it's just a matter of basic troubleshooting to address each case individually