3CX Webclient on TS & Headsets

[SeerzLiam]

Hello,

For a client we have the following setup.
We performed a recent migration of their network to work on a locally installed Terminal Server.
The terminal server will house their applications and files, so working locally will be minimalized.
Currently they are running on the softphone software of another provider and we have learned their software is not compatible with Terminal Server.
They do not have any physical phones.

We would like to offer them an alternative with 3CX.
They are all using Plantronics Savi 140 headsets and have experience working with software to administrate their calls.
The Webclient will serve almost all purposes they require however we are having difficulties with making the webclient use their headset/microphone for phonecalls.
We are currently testing this on our own Terminal Server and I would likr to know the following:

• Is it possible to perform phonecalls using the webclient, while using the redirected local device thats found on the terminal server?
• Can this be done with generic headsets or must this be specific brands and types?
• Is it at all interesting for us to use the 3CX Windows App instead of, or together with the webclient to support as much possibilities as possible? As far as I know the 3CX Windows App is being phased out.

We have a generic Logitech headset available for testing and will likely also have Plantronics headset available for testing soon.

Thank you for your responses.

 

[Evolute IT]

Just a thought: why use TS instead of RemoteApp or RDSM(RDP)? TS is old and doesn't work with most things.

 

[JohnS_3CX]

You don't need any specific headsets if you answer the phone using the webclient interface.

I expect it should work so long as you are running chrome and chrome can detect a mic and speaker on the machine it is running on. If it is a redirected device, this will depend on the server and its own interfaces, but you can test it using a demo system to see how it behaves and make some internal calls. Remember, the web client is not really aware of your system to such a degree, but it rather asks your browser for an audio in and out device so it can do its job and if those devices send audio it should be ok.

 

[SeerzLiam]

You don't need any specific headsets if you answer the phone using the webclient interface.

I expect it should work so long as you are running chrome and chrome can detect a mic and speaker on the machine it is running on. If it is a redirected device, this will depend on the server and its own interfaces, but you can test it using a demo system to see how it behaves and make some internal calls. Remember, the web client is not really aware of your system to such a degree, but it rather asks your browser for an audio in and out device so it can do its job and if those devices send audio it should be ok.

You are right. I managed to get the webclient working for the devices and it works quite well.
However it seems like I cannot pick up the calls with the button on the headset. This works with the Windows 3CX App, I still have to test if this works on a Terminal Server, but I fear it probably won't work because it just finds it as a redirected device and not as "Plantronics Headset".

 

[JohnS_3CX]

Exactly, if the device is not local. Passing audio straight from your local pc to the remote pc will not allow this to work. The device needs to be physically plugged into the remote machine which is not possible in this scenario.

You can pick up though using the notification that pops up on the webclient, or the notification/toast that appears on your windows 10 desktop of the remote machine.