Problem with Yealink DECT handsets registration sequence

[3CXfan]

After reading 3CX's guide on Provision Yealink DECT Base, I successfully added Yealink W60B to 3CX under FXS/DECT. Then I followed 3CX's guide on Registering Yealink handset to DECT Base and successfully paired 3 units of W53H to extensions 801, 802, 803 so far.

Unfortunately I am currently stuck, not knowing how to register W56H as Handset #8 (extension 808) first before I have access to and register 4 additional units of W53H (to be assigned to extensions 804, 805, 806 and 807).

This is a problem because It seems handsets can only be paired/registered in the same sequence provisioned by 3CX, and I haven't been able to find a way to register Handset 8 (808) FIRST before the 4 other handsets that I haven't purchased yet. I have tested and noticed that if I press "Start Registering" after only 3 handsets have been registered, W60B will simply register the next one as Handset 4 (804), not Handset 8 (808).

Is there a way to solve this? I haven't found a way to re-assign handsets or change their sequence once they are registered. Help is appreciated.

• 3CX Version, Standard Annual 16.0.9
• Server OS, Windows 10
• Is the 3CX Server Hosted and where? Not Hosted
• IP Phones:
  • Yealink W60B
  • Yealink W56H
  • Yealink W53H
• Provisioning Method: Local
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: N

 

[cobaltit]

That sounds like a Yealink limitation, not 3CX. But just register it as the 4th Handset using extension 808 and re-register it when you get the other ones?

 

[3CXfan]

That sounds like a Yealink limitation, not 3CX. But just register it as the 4th Handset using extension 808 and re-register it when you get the other ones?

I thought about this, but people won't be too happy if I introduce down time once it's up and running and besides who knows what else will go wrong in the process so I am hesitant to do this.

Additionally, will registering and de-registering affect voicemail, recordings, ring groups and call history etc?

 

[cobaltit]

Registering is the act of tying a SIP endpoint to an extension. Everything you mentioned is extension related so as long as you don't delete the extension, nothing else will be affected.

 

[JohnS_3CX]

The issue is that you want to set it up in a way the manufacturer did not intend, so go ahead and set them up for now so you can have them running, and when the time comes to make the changes it will take you no longer than 5 mins. Especially when you have had some practice beforehand so you know exactly what to expect from the device behaviour.

 

[AWS2P]

I'm not seing any problem with 808 handset being in 4th position, what is the problem you get with this ? just is not seen in extension order ?

even if you don't have the handset for now , you can set extensions to be provisionned and so 808 could be in last.
already done this in other brand "Gigaset" client wanted new extension ready to use, he just needed to pair a new handset on dect base to use new preset extension.

 

[3CXfan]

I'm not seing any problem with 808 handset being in 4th position, what is the problem you get with this ? just is not seen in extension order ?

even if you don't have the handset for now , you can set extensions to be provisionned and so 808 could be in last.
already done this in other brand "Gigaset" client wanted new extension ready to use, he just needed to pair a new handset on dect base to use new preset extension.

Maybe Gigaset is more flexible than Yealink in that you could pair a DECT handset to the base out of sequence, but Yealink doesn't offer this option, ie. it locks Handset # to "Handset 4" if that happens to be the next handset to pair, instead of letting users choose "Handset 8" for extension 808. This leaves no option to reserve Handset 4, 5, 6 and so on for extensions that are missing handsets in the meantime, ie. 804, 805, 806.

Based on the feedback on this thread though, I should just learn to improve my provisioning speed when I do have to add handsets and switch thier sequences later. Hopefully there won't be other complications that arise during re-pairing and re-sequencing!

Question: Does multiple provisioning on the same Yealink base/devices increase the chance of breaking something?

 

[3CXfan]

I did what was suggested here and encountered an issue already.

The following steps can duplicate the issue:

I went to 3CX FXS/DECT > Yealink W60B > Extensions and remove the attached extensions that still do not have handsets, so now #808 is in Extension slot / drop-down menu 4 on 3CX side.

Then I went to Yealink W60B webpage > Settings > Auto Provision and pressed "Auto Provision Now" and can see that Account 4 on Yealink has been correctly provisioned to #808

But Yealink "Accounts" 5-8 are still populated with previous 3CX extensions despite that the corresponding 3CX slots 5-8 are already set to "Empty" on 3CX.

What is the correct way to provision Yealink W60B via 3CX so empty slots on 3CX Extensions will not have weird previously provisioned information? In other words, how to wipe out the previous extensions that have been provisioned, it doesn't seem choosing "Empty" works.

 

[3CXfan]

Another side effect of using 3CX to make changes that require provisioning again on Yealink W60B is:

Custom Handset Names on Yealink W60B do not survive.

Something for others to be aware of if you rely on custom names of handsets to keep track of handsets. For my W60B it's only max of 8 handsets so it's not a big deal but I can't imagine a nightmare on their higher model bases that support up to 250 devices to find all custom names wiped with re-provisioning.

 

[3CXfan]

In conclusion, re-provisioning a new sequence multiple times works but there are multiple caveats to be aware of and requiring attention. I hope the above information will be of use to whoever stumbling onto this same scenario in the future.

 

[AWS2P]

perhaps simplest way is to factory reset base and do a provisioning like it was the first time with a full set of handset

 

[AWS2P]

To be sure it was working same as Gigaset base, i did a try on one w60B i have for demo

So initially that DECT BASE was set with 2 accounts (ext 105, ext113) but only one handset for 105


I added to the 2 first existing extensions, 102, 103,104,106, empty, 111 then forced to provision from W60B GUI and checked if acounts were or not pushed by provisioning, and you know what ... everything is there as the same behavior on Gigaset.

I think you probably mix between accounts and handsets.
SO finally you can preset what you want even if you don't have any handset and just pair them once you get them .

 

[3CXfan]

To be sure it was working same as Gigaset base, i did a try on one w60B i have for demo...

... everything is there as the same behavior on Gigaset.

I think you probably mix between accounts and handsets.
SO finally you can preset what you want even if you don't have any handset and just pair them once you get them .

Hi, thanks for testing and reporting.

No, I did not mix up accounts or handsets.

I have no issues pushing all or some handsets to Yealink W60B, but the actual issues are:

Pairing new phones have to be done in the exact same sequence of what's on 3CX so for example, I cannot pair a DECT phone in position/slot 6 before 4 and 5, because Yealink W60B will automatically pair it to slot 4.

 

[AWS2P]

I don't understand what sort of problem it is with having extensions not in a strict order on DECT base , you just need to have it provisionned and handset paired to have it working .

Is it because you like things stricly in right increasing order on dect base ?

some of my customers asked me to add more extensions than they use since first install of pbx , they have not full number of handset but base is already preset , so tomorrow they want a new handset, just pair a new one and set it to a free extension , done.

 

[AWS2P]

Pairing new phones have to be done in the exact same sequence of what's on 3CX so for example, I cannot pair a DECT phone in position/slot 6 before 4 and 5, because Yealink W60B will automatically pair it to slot 4.

No, on my test it was like screen copy pasted previously, and so ext 111 was in last slot just before an empty space, no problem to set in any order you want

 

[3CXfan]

No, on my test it was like screen copy pasted previously, and so ext 111 was in last slot just before an empty space, no problem to set in any order you want

That's correct, on 3CX, I can set whatever order I want, but during pairing of Yealink handsets, W60B only allows sequential pairing. You cannot pair a handset as #8 before before all preceding handsets.