WH62/WH63 DECT headsets with Yealink T3 series

[Stephen Hellriegel]

Looking to use a WH62/WH63 series DECT wireless headset work with Yealink EHS35 adapter with T3 series phone?

I bought $800 worth of headsets and adapters since everything on Yealink's site indicated fully supported.

As of 3CX V18 update 6:

1. 3CX does not support the EHS35 adapter to integrate the Yealink WH62/63 headset family.
2. The Yealink phone firmware "supported" by 3CX does support the EHS35 adapter.
3. T3 series phone firmware needs to be 124.85.0.0 or newer

There is a provisioning parameter needed in the provisioning file 3CX generates to configure the phone (the template).
Knowledge article on Yealink site

voice.ultrasonic.enable = 1

• The T3x series templates are embedded in the yealinkT4x.ph.xml file
• 3CX requires Pro or Enterprise editions to use custom templates
• 3CX support will require you to reconfigure the phone back to a "non-custom" template before they support you
• T3 series phones without an EHS35 adapter plugged in work normally with the voice.ultrasonic.enable set to 1
• The adapter is "1. Common" in the "Analog Headset Adapter" basic settings on the phone.

Hopefully 3CX will add this parameter to the template and push quickly to the world.
I used 3CX template syntax so the parameter is only added for the supported T3 series phones.
The EHS35 deficiency with 3CX has been a reported defect in the forums since Nov 2021.

I avoid running unsupported templates. I hate disappointing customers even more.

Here is the bottom of my modified yealinkT4x.ph.xml.

   phone_setting.idle_dsskey_and_title.transparency=

   #Custom Code Block
   #Add EHS35 headset adapter support to T3x series
   {IF ua=SIP-T30P,SIP-T31P,SIP-T31G,SIP-T33P,SIP-T33G}
     voice.ultrasonic.enable = 1
   {ENDIF}
   #End Custom Code Block

]]></deviceconfig>
    </device>

 

[JohnS_3CX]

Hi Stephen,

We would like to clarify that 3CX does not provide support for phone peripherals, and we do not carry out any testing on them for compatibility so I don't foresee us adding any new parameters to cover this requirement.


Just as an FYI, Yealink is solely responsible for testing and providing firmware to 3CX.

So as a Yealink customer yourself, I think this request is best addressed towards Yealink. If they include support for it in the next firmware release they give us then it will work straight "out of the box" for you as soon as we push out the next firmware.

 

[Stephen Hellriegel]

Hi Stephen,

We would like to clarify that 3CX does not provide support for phone peripherals, and we do not carry out any testing on them for compatibility so I don't foresee us adding any new parameters to cover this requirement.


Just as an FYI, Yealink is solely responsible for testing and providing firmware to 3CX.

So as a Yealink customer yourself, I think this request is best addressed towards Yealink. If they include support for it in the next firmware release they give us then it will work straight "out of the box" for you as soon as we push out the next firmware.

John
Let me counter clarify as I don't believe you understand the 3CX position on this particular topic.

3CX supports sidecar BLF expansion peripherals. These phone peripherals provisioned via the template for phones.
3CX supports Yealink T3x phones.
3CX announced support of the WH62 headsets.

Are you clarifying that 3CX doesn't intend to support WH62X phone headsets? See below:


Please re-read my original post with the eyes of understanding that I am giving 3CX a fix for something 3CX claimed support of.

It makes no sense for me to contact Yealink, I don't have any support channels, or engineering contacts.

I suppose 3CX can go to Yealink and ask them to change the default parameter for T3 series, QA new firmware, push new firmware globally, wait for 3CX to QA firmware, and wait for a release to include update, then update my phones.

Or, 3CX can do what their template/provisioning system was designed to do. Seriously, this is exactly the thing 3CX templates are meant to be able to handle. There isn't much for 3CX to do other than ctrl-c ctrl-v, pretty up the commenting to be consistent with 3CX formatting. (I intentionally used a comment format that was different), run a syntax parser test on the template (your developers do have a lint rule file for 3CX template language in BNF format, right?). Run a test on a T4 series to see it isn't broken, run a test of T3 series phone to see it isn't broken. Done. Release as a template update, which we get all the time. 3CX doesn't even need to spend the $200 to buy an EHS35 and a WH62 headset,

 

[Stephen Hellriegel]

Hold my beer. This is way more complicated, we are both wrong.
The new Yealink T3 series firmware supports four styles of headsets. I will look at extending my template patch to include a pull down that will show up in the provisioning tab for the phone in 3CX. This needs to be a per user/phone instance parameter, it cannot be globally applied. I don't even know if 3CX overwrites the headset.
It really seems 3CX needs to have a "headset type" in the provisioning menu for Yealink phones, and does the right thing.

 

[mcsphones]

So I too sell these headset series, but we'd only done them with T4(U) and higher models. Until we had one customer with a T3 series want one, so we ordered the appropriate adapters. Then we found out we had to update firmware, etc. While it's unfortunate that Yealink didn't readily provide support for the headsets with the T3 series out of the box, it isn't really a 3CX issue.

 

[JohnS_3CX]

3CX announced support of the WH62 headsets.

When we talk about headset integration in 3CX, we mean that this is for the desktop app and webclient (we added an integration so the headset buttons will work with our client).

As mentioned earlier, we do not provide support for headsets on IP Phones and never did before AFAIK. Please contact Yealink about this to get it added if you wish to do so - as a Yealink customer you can request features directly from them, and if they add it into the firmware (which in all likelihood they will) then we will publish it as soon as they update the templates, the firmware files and perform the testing with 3CX as is our usual procedure with all IP phone manufacturers.

I would like to make it abundantly clear that the IP Phone manufacturers are responsible for creating and maintaining the templates and firmware, and carrying out the interop testing with 3CX. We can then later publish it once they've completed their part.

 

[SteveITS]

Following up on the posts above, do the Yealink headsets work with T5x series phones under 3CX? I was installing phones Friday and then they asked about headsets. Obviously there's the Desktop App etc, but they already have the phones...
Thanks,

 

[SweetAction]

3CX doesn't care about headsets connected to the phone - 3CX doesn't speak to the headset in that case, the phone does. So supported phone with a headset supported by the phone manufacturer will be fine.

I can't imagine that Yealink Phones with Yealink Headsets wouldn't work.

 

[CentrexJ]

Following up on the posts above, do the Yealink headsets work with T5x series phones under 3CX? I was installing phones Friday and then they asked about headsets. Obviously there's the Desktop App etc, but they already have the phones...
Thanks,

Yes they work amazing with currently manufactured T4xU and T5x phones. The issue above was an issue with the T3 model phone which is their bottom tier phone of which the headset would be more expensive than the phone itself and still need an adapter.

 

[SteveITS]

Great, thank you both for confirming, just wanted to double check!