Yealink DECT Phones | Configuration Guide

[KaterinaK_3CX]

Supported models:

• Yealink W60B
• Yealink W70B
• Yealink W80B / DM
• Yealink W90B / DM

Read the guide.

 

[gigaboy]

It would be nice if this explanation were for self hosted (diagrams shown are for cloud). I've struggled for three days to get this to work with a w70b base and w56h handsets. Reset the handsets, updated the firmware on the handsets and dect base. Handsets will not communicate with base. Dashboard for phones shows UNPROVISIONED. User shows as active, but phones won't ring. Wiped and repeated three times, still not working. I never had this trouble with the "bricked" w52b units.

 

[JohnS_3CX]

@gigaboy go ahead and start a new Thread under the IP Phones > Yealink category and we can help out.

 

[David Forster]

Hi Katerina,

Thanks for the info, it was useful to double check I'm doing ti the right way ;-)

I've just moved a customer onto using the new web clients as opposed to the legacy desktop app and see that the DECT handset is not an option to be controlled by the app (it was/is on the legacy desktop app), is there a work around for this, or is this planned to be added etc.? Otherwise I'll have to get them all to go back to the old desktop app.

The image below shows what I mean, only 2 deskphones and browser and smartphone showing despite the extension also having a DECT handset. (the legacy desktop app shows them all including the DECT handset)

Regards,

David.

Web client



Legacy desktop app

 

[JohnS_3CX]

Hi Katerina,

Thanks for the info, it was useful to double check I'm doing ti the right way ;-)

I've just moved a customer onto using the new web clients as opposed to the legacy desktop app and see that the DECT handset is not an option to be controlled by the app (it was/is on the legacy desktop app), is there a work around for this, or is this planned to be added etc.? Otherwise I'll have to get them all to go back to the old desktop app.

The image below shows what I mean, only 2 deskphones and browser and smartphone showing despite the extension also having a DECT handset. (the legacy desktop app shows them all including the DECT handset)

Regards,

David.

Web client

View attachment 35712

Legacy desktop app

View attachment 35713

Hi David,

The legacy app was using a legacy protocol that made that possible regardless of what endpoints were used.

This method was never supported on the Web client or Desktop app and there are no plans to change this in the future.

If you want to keep using that feature, I'm afraid that the only way to do so will be via the legacy app.

 

[David Forster]

Hi David,

The legacy app was using a legacy protocol that made that possible regardless of what endpoints were used.

This method was never supported on the Web client or Desktop app and there are no plans to change this in the future.

If you want to keep using that feature, I'm afraid that the only way to do so will be via the legacy app.

Hi John,

Thanks for the super quick reply

I certainly should have done my research before moving them from the legacy app to the new app and web client, I'd just assumed this functionality would have been migrated over and included. I should have learnt the 'never assume' lesson by now.

Obviously with the legacy app being called 'legacy' the expectation is it will one day be retired, hence my reasoning to start to move customers over, and DECT handsets are becoming the device of choice for many small businesses where users aren't tied to their desks all the time but also don't want to be using their mobile app all day long.

Appreciate I'm not allowed to make suggestions or feature requests, but if there is any way of taking this feedback into account I'd be most appreciated. I'm sure there are lots of installs out there with a decent sized DECT estate unaware this functionality will be lost.

Many thanks,

David.

 

[Hermicus]

Update for this manual : https://www.3cx.com/sip-phones/yealink-dect-phones/

W80DM in combination with W56H Handset - Important is to register first the handsets to the DECT Manage before Provisioning with 3CX - otherwise you are not able to register any handset.

 

[Robert S]

Hi all,
I have two Yealink W90DM (Dect Managers), one W90B (Base) and one W73H (Phone).

When configuring one Dect Manager, Base and Phone everything works fine, using provisioning as the manual writes.

I want to use the Yealink DM Backup option.
An additional DM is required (my second Dect Manager), and it is configured as a backup DM in the system. When the main DM is abnormal, the backup DM can immediately take over all the base and handsets in the system to ensure that the system can still work normally.

If I configure the second Dect Manager as DM-Reserve and register this on the primairy DM, It gives the Status Connected. Looks good so far.

FAILURE: But if I unplug the primairy DM, to test the failover, It does not come back online. The DECT light on the second DM and base are not green.

To be sure, I tested if the firmware (Lydis 130.87.188.1) and settings work without provisioning to 3CX.
And then within a few minutes, the Reserve DM is online and the DECT light is green on the second DM and Base.

QUESTION: Does some knows if DM backup solution works in combination with 3CX? If yes, how to configure this.

Kind regards, Robert

 

[JohnS_3CX]

Hi all,
I have two Yealink W90DM (Dect Managers), one W90B (Base) and one W73H (Phone).

When configuring one Dect Manager, Base and Phone everything works fine, using provisioning as the manual writes.

I want to use the Yealink DM Backup option.
An additional DM is required (my second Dect Manager), and it is configured as a backup DM in the system. When the main DM is abnormal, the backup DM can immediately take over all the base and handsets in the system to ensure that the system can still work normally.

If I configure the second Dect Manager as DM-Reserve and register this on the primairy DM, It gives the Status Connected. Looks good so far.

FAILURE: But if I unplug the primairy DM, to test the failover, It does not come back online. The DECT light on the second DM and base are not green.

To be sure, I tested if the firmware (Lydis 130.87.188.1) and settings work without provisioning to 3CX.
And then within a few minutes, the Reserve DM is online and the DECT light is green on the second DM and Base.

QUESTION: Does some knows if DM backup solution works in combination with 3CX? If yes, how to configure this.

Kind regards, Robert

Hi Robert,

1. Please note that only this firmware here has been interop tested for 3CX by us.
https://www.yealink.com/en/solution-detail/resource-for-3cx

2. That backup feature is out of our scope, and therefore has not been validated by us.
We recommend to speak directly with Yealink Support instead. It may not be compatible at all with 3CX.

 

[Robert S]

Hi John,
Thank you for answering.

1. I also tested with firmware version 130.87.0.10.
2. I already created a ticket at Yealink.

Could you please confirm the following:
If DM1 is registered with his MAC Address. Can reserve DM2, which has another MAC Address, sign in on 3CX with the configuration settings of DM1?
If not, in which log can I find this denied message?

 

[Robert S]

Hi Robert,

1. Please note that only this firmware here has been interop tested for 3CX by us.
https://www.yealink.com/en/solution-detail/resource-for-3cx

2. That backup feature is out of our scope, and therefore has not been validated by us.
We recommend to speak directly with Yealink Support instead. It may not be compatible at all with 3CX.

My support partner told me this:
A MAC address is only required for active use from central provisioning. A device with the exact same configuration but a different MAC should be able to register with SIP just fine. However, you won't be able to make any changes since provisioning won't work.

IT WORKS !
A few days later I received a new firmware version from Lydis for the W90DM, version 130.87.188.202.
This works completely as desired. After 2 minutes the failover is finished and everything is online.