@patrickb_de The PWA is the web client, just using Google technology to make it feel like an app. To all intents and purposes its the web client. Its literally the same code. Just running in an app like environment. The universal driver is based on web tech so not compatible with the windows softphone so it can never make it into the windows softphone which is native windows code. Personally I am not sure how useful the universal driver is and not sure how many no name brands have really tested it with the driver. Also if you sell it it must keeping working for many years and that's a whole nother discussion.
Keep in mind this headset integration is only for accepting calls via a button on the headset. Using a headset for microphone and earpiece you can use any headsets or device you like. I am not sure but I get the impression that you are referring to normal headsets you can use absolutely fine when at your desk.
The headset integration is only needed if you want to take calls whilst away from your desk. personally I don't think its worth it use a normal wired headset as keep in mind these headsets use DECT and I wouldn't want a DECT transmitter in my ear all day. But that's just me. Also they are expensive and the windows drivers they require are support intensive. And as an alternative just bring along your mobile when away from your desk and take the call on that.
Off the record (here on the forum
) if you really must have a headset with headset integration use JABRA. Its the manufacturer with consistent tech support, they communicate with us. We don't agree on everything but they are "there".
I know the underlying technology is the same, but I’ve never seen the universal driver in the Web Client headset integration section.
Every type of headset I sell to customers is one I’ve personally tested beforehand. For example, the current Yealink series is too heavy to wear for hours. The older WH62/66 models were also heavy, but not as heavy as the new 64 series. The comfort of placing the headset back into the base was also better on the older models with the magnetic charger compared to the Jabra-inspired design on the 64 base. Some of my customers, as well as myself, simply don’t want to use these new, heavier headsets. Poly models are also too heavy for most of my customers.
So, moving on to the next brand: Jabra. They offer good build quality and lightweight headsets, but technically they have some issues that are uncomfortable for users in their daily work. For example, I switched to an Engage 75 Mono around four weeks ago because I wanted triple connectivity. Lightweight: check. Good build and sound quality: check. Bluetooth for my mobile phone: check. But that’s where one of the biggest issues starts: the Jabra stays connected to the mobile phone’s Bluetooth even when it’s placed in the base.
So if you’re walking around your office or home and you come back into Bluetooth range, the headset will pick up your mobile calls and route the audio to the Jabra - even though it’s still in the base (Yealink does this as well). That’s really annoying if you’re used to your headset only connecting to your phone when you take it out of the base, like it works with EPOS headsets such as the IMPACT SDW series, which are also lighter and have good sound quality.
Also, if you use the overhead mono versions of Jabra headsets, many of them tend to slip down from your head during long calls while walking through the office (Germans love to walk around the office during long calls - and multitask while they’re at it.
). I don’t know if the 10g difference between the SDW 10 HS and the Engage SE makes the difference, but it’s possible.
If you press the mute button on the Engage on top of the microphone, the customer can hear the clicking and touching noises beforehand. Yealink’s and EPOS’s ‘flip-to-mute’ technology is better in this regard.
These small details make a huge difference in daily use.
For me, it’s clear that I should only use and sell the officially supported “named brand” headsets to ensure they work reliably for years. But in the past, EPOS was one of the supported brands and in version 18 they work over the universal driver. I sold many of them to customers, and they’re happy with them—they don’t want to switch to Jabra, Yealink or Poly because of the issues I described. And yes, if you’ve bought a 200€ to 300€ headset, you definitely want to use the buttons on the headset to answer incoming calls.
But if the web client supports the universal driver, these customers will definitely stick with it until their headsets fall apart. I’ll check that for my “sticky EPOS customers”
