Issue with plantronics hub

[Jeff Harlan]

In order for the extension to recognize the headset in the new edge we have to go to https://127.0.0.1:32018/spokes/deviceservices/info each morning. Can anyone explain what this is and is there a way to force this to happen without the user having to do anything?

 

[cjt]

In order for the extension to recognize the headset in the new edge we have to go to https://127.0.0.1:32018/spokes/deviceservices/info each morning. Can anyone explain what this is and is there a way to force this to happen without the user having to do anything?

We also have this issue using the webclient with plantronics headset integration. I believe it only happened after upgrading Plantronics Hub to 3.18. After going to the web address you mention, the headset initialises, but a warning is displayed in the 3cx webclient about an unsecure connection.

It would be great if the cause could be identified and resolved.

 

[JohnS_3CX]

Sennheiser recently faced a similar issue, because Chrome no longer accepts older SSL versions. So if the Plantronics service runs TLS 1.0 for example, it will also be affected unless you bypass the Chrome restriction. The security warning you mentioned seems to point in that direction