Jump to content

Windows App - Yealink WH6 DECT Headsets


VitaminJ

Recommended Posts

This is a question that's been asked a few times in different forms;

Is there a way to use the buttons on a Yealink WH6 series headset to answer calls in the Vodia App? I note there's a blog post about Vodia interoperability with these specific headsets - but I can't find a way to get the buttons working. Audio works fine as they're a Windows audio device.

VODIA ANNOUNCES INTEROPERABILITY WITH THE YEALINK WH6 DECT WIRELESS HEADSET SERIES

Can you shed some light on this?

Link to comment
Share on other sites

We are actually working on HID devices in the front end. Unfortunately there is no such thing as a common standard for different devices. That is why things like PTT on a headset will remain difficult for the foreseeable future. It seems that Bluetooth is going a different direction, especially on Apple devices PTT is defined outside of the apps anyway. Foe Android devices bluetooth is now in the hands of the Google calls library, a step forward compared to before especially compared to the disconnect behavior but still lagging behind with what can be done on HID compatible USB devices. Anyhow, try the latest 69.0.3 if you want to see where we are today.

Link to comment
Share on other sites

  • 1 month later...
  • 1 year later...

We are on 69.3.2 (not from choice) and we are still looking for Bluetooth headset remote pickup/hang-up.  Teams headsets work on the Teams Windows app for remote call handling, but we need the same functionality using the Vodia Windows app.  Is this an impossible request or not popular enough to warrant development?  

Link to comment
Share on other sites

No, it's a very reasonable request. Before this, the headset buttons would just give a code and we would map it to some function based on the app context, and it worked nicely (some still do it that way and should work).

However, now everybody has introduced status based protocols meaning the headset has to have the context of the call (ringing, connected, idle, etc.) with bi-directional communication.

Of course it's very possible to do but we just need some time and also to understand if everyone is doing it differently or following some generic protocol (for a change).

And with many other things on our plate, it hasn't been on top priority either but now we see more demand and looking into a more complete silution.

Thanks.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...