Hello there,
we are trying to deploy a new 3CX Pro PBX for one of our customers.
The customer already uses ESTOS ProCall with DATEV contact replication via MetaDirectory.
They work on terminalserver based systems and are using an Alcatel IP Softphone on the local workstation to dial when they are at home.
The customer wants to mainly use yealink wh67 headsets. According to yealink.com these work for the v16 client with a plugin yealink provides.
We have a testing environment with the following configuration:
- 3cx with the alternative tapi server from t38printer.de installed
- v16 client installed locally on a client with the v16 yealink plugin in place
- ESTOS UCServer (management server for procall) with the t38printer.de tapi service provider installed and a user with a configured 3cx tapi line
- server 2016 terminalserver with ESTOS ProCall installed
What works:
- An incoming call gets recognized over the tapi line and inside estos
- Incoming calls get displayed in the wh67 headset display
What doesnt (this is an important feature for the customer):
with ESTOS ProCall you can initiate a call from any source, e-mail, website and most importantly the DATEV software.
If we click or select a number to dial, we get a call from "MakeCall" on the local client (which is not visible because the user is currently logged in on the rds farm). The headset display stays idle and we cannot answer the call via touchscreen or the hardware button on the headset itself.
resources:
link to the yealink support plugin for the v16 windows client:
https://support.yealink.com/en/portal/docDetail?documentCode=ab40bad95d47c7c9
screenshot from yealink support for wh66/67:
is there someone who has a similar config or knows why the "MakeCall"-call is not like a incoming call, which does work as you can see above.
we are thankful for every hint, thank you in advance!
sincerely
Kevin Braun
we are trying to deploy a new 3CX Pro PBX for one of our customers.
The customer already uses ESTOS ProCall with DATEV contact replication via MetaDirectory.
They work on terminalserver based systems and are using an Alcatel IP Softphone on the local workstation to dial when they are at home.
The customer wants to mainly use yealink wh67 headsets. According to yealink.com these work for the v16 client with a plugin yealink provides.
We have a testing environment with the following configuration:
- 3cx with the alternative tapi server from t38printer.de installed
- v16 client installed locally on a client with the v16 yealink plugin in place
- ESTOS UCServer (management server for procall) with the t38printer.de tapi service provider installed and a user with a configured 3cx tapi line
- server 2016 terminalserver with ESTOS ProCall installed
What works:
- An incoming call gets recognized over the tapi line and inside estos
- Incoming calls get displayed in the wh67 headset display
What doesnt (this is an important feature for the customer):
with ESTOS ProCall you can initiate a call from any source, e-mail, website and most importantly the DATEV software.
If we click or select a number to dial, we get a call from "MakeCall" on the local client (which is not visible because the user is currently logged in on the rds farm). The headset display stays idle and we cannot answer the call via touchscreen or the hardware button on the headset itself.
resources:
link to the yealink support plugin for the v16 windows client:
https://support.yealink.com/en/portal/docDetail?documentCode=ab40bad95d47c7c9
screenshot from yealink support for wh66/67:
is there someone who has a similar config or knows why the "MakeCall"-call is not like a incoming call, which does work as you can see above.
we are thankful for every hint, thank you in advance!
sincerely
Kevin Braun
