Problems with EPOS Connect & 3CX Webclient

[eagle37]

I am using 3CX with a EPOS MB Pro 1 UC ML headset. When I first installed this headset 2-3 days ago, it was working fine, and in the softphone configuration of EPOS connect, 3CX Webclient was configured as the default device. Now the default softphone configuration is blank in EPOS connect, 3CX webclient is no longer a selection, and the headset is working inconsistently. I've tried uninstalling and reinstalling EPOS connect, the EPOS 3cx plugin, the chrome browser plugin, and reconfiguring the EPOS integration in the 3CX web-client. No luck with any of these.

EPOS Connect 4.2.2.1053
BTD 800 2.15.8
MB Pro 1 2.6.16
3CX 16.0.1078

Any help is appreciated. Thank you

 

[SteveITS]

The web client and Chrome extensions use different (their own) settings. So if you're using the extension the web client settings are not applicable, and vice versa. In other words to use the web client settings disable the browser extension.
To activate/set the audio settings in the extension, select Browser Extension as the active phone in the web client (upper right of the page.) Or set Web Client and don't use the extension.

 

[eagle37]

Steve, I'm sorry. This may be the intended design, but my experience is proving otherwise.
The browser extension is selected in my 3cx web client:



I see this message

But the browser extension settings are being ignored.
The web client settings are the controlling settings proved by what I am physically experiencing, but the web client settings are disabled because the browser extension is supposed to be the controlling device. Things only work as expected when I forcefully override the web client settings with the browser extension enabled.

 

[SteveITS]

But the browser extension settings are being ignored

I understand what you're saying now. That is odd, they shouldn't cross over. I believe the extension stays running by default, if Chrome is closed...have you tried the brute force method and logged out of Windows?

 

[eagle37]

I'm not sure what you mean by the "brute force" method? Once I forcefully set the headset integration and set the default speakers in windows to the MB Pro, the headset will work. It does not lose the headset integration configuration in the web client. The headset integration is not set or lost by changing the integration in the web extension. Whatever setting is in the web extension is just ignored. Whatever setting is specified in the web client is what works. If I don't log out of the 3cx web client and just close Chrome and the web extension, the headset will still work and receive a call - is this what you are asking?

 

[SteveITS]

re: "brute force" I was being a bit tongue-in-cheek. I just meant log out of Windows to start fresh. Or reboot.

Another item of note to clarify, the integration setting in any client affects (basically) whether the headset button works, not where sound goes. Perhaps delete and reinstall the Chrome extension?

If I don't log out of the 3cx web client and just close Chrome and the web extension, the headset will still work and receive a call

It's likely still running in the system tray.

 

[eagle37]

Yes, I've rebooted numerous times while removing and reinstalling all involved software at the beginning of the troubleshooting process. The headset was unable to receive/answer a call without the integration set to Sennheiser in the web client. This was also true if answered via the browser extension and not via the headset button. The browser extension would answer the call and both sides of the call would just her silence.