Sennheiser Headset Integration Not Working in Edge After 2020-07 Windows Update

Status
Not open for further replies.

dlarson

Forum User
Joined
Feb 21, 2020
Messages
14
Reaction score
7
We had been using the Sennheiser headset integration in Edge (Chromium) browser extension for several weeks without problem. Yesterday, we had a couple of users getting "Error connecting to HeadSetup Pro" in the Edge browser extension. Both of them had the 2020-07 Windows 10 cumulative update (for 1909/2004 & .net framework) applied. Mine integration was still working but I hadn't had the 2020-07 updates applied. Last night I restarted to apply the 2020-07 updates and the headset integration was still working afterwards, so I shut down. After starting up this morning, I am now receiving the same error.

We have tried reinstalling the browser extension, but nothing seems to work. I did try using Chrome and that one does work, so it seems to be a problem only with Edge.

Has anyone else seen this problem?
 
I also reported to Sennheiser/Epos and received this back, in case it helps:

" Yes it is true that we have a call control issue with 3CX Web client after the latest Chrome update that deprecated TLS 1.0 and TLS 1.1"
 
I'm not saying this is a good idea but it does work. You can force Chrome 84 to allow legacy TLS versions. Chrome deprecated the legacy versions because of potential security risks so keep that in mind.
Software manufacturers like Sennheiser have had plenty of advance warning about the change and should have modified their software to be compatible with a compliant version of TLS prior to the release of Chrome 84. 3CX didn't do anything wrong and I'd hate to see them remove Sennheiser as a supported product over a correctable issue on the manufacturer's part.
 
  • Like
Reactions: NicholasP_3CX
Christopher Kurek (EPOS Enterprise)

27.07.2020, 12:24 UTC

Hallo Herr Müller,

anbei der temporäre Workaround.
Einen Fix spielen wir am 03.09.2020 über ein EPOS Connect Update ein.
 

Attachments

I also opened a ticket in EPOS, they working on it.
Curently the solution of IT Planungsgruppe is working for the moment but still waiting a new fix from 3cx or Epos.
 
As a follow up, I was told by EPOS Global Support that this will be fixed in an update scheduled for release on September 3rd, 2020. As a workaround, you can modify flags in both Chrome and Edge to not enforce the deprecation of legacy TLS:
  1. Open up your browser
  2. In the address bar:
    1. For Edge, key in edge://flags
    2. For Chrome, key in chrome://flags
  3. Type TLS into the search control.
  4. Find the “Enforce deprecation of legacy TLS versions” setting and change it from Default to Disabled. A button will then pop up to restart your browser.
This worked for us but we'll need to remember to reverse this setting after the EPOS Connect update.
 
Here a workarround for you until sennheiser has fixed this issueworkarround_epos.png
 
The EPOS update should now be out, please proceed to update it and you should able to use the integration again

1599565104330.png
 
Status
Not open for further replies.

Forum statistics

Threads
112,025
Messages
590,367
Members
164,976
Latest member
Roman Mazur