Solved Yealink W60B Provisioning

[Dennis Pillow]

I can only imagine that I am missing something in the provisioning task of the W60B. My question is, "Is there any simple guide or file to show me the proper way to configure a W60B for provisioning on the 3CX Cloud Service"?

 

[accentlogic]

Setup two of them today. Read both articles completely, and follow the links for more info.

Basically, get the MAC for your W60B, in the console go to Advanced, FXS/DECT, and add the DECT base unit. Then connect to the W60B web interface and past in the provisioning URL. After it has registered with 3CX the rest of the guides should get you there.

https://www.3cx.com/sip-phones/manually-provision-yealink-dect/

https://www.3cx.com/sip-phones/yealink-dect-w52p/

 

[Dennis Pillow]

I thank you for the reply but my problem is in the initial connection to 3CX Cloud. I can't get it to register.

 

[Saqqara]

How are you trying to provision the phone - sbc or stun

make sure you select the correct ‘provisioning method’

 

[Dennis Pillow]

Stun. I have reset the W60B to factory and used STUN to provision. It finally connected but dropped off again. This happens each time I do this. It will be registered for a short time and then Boom....It's disconnected.

 

[Saqqara]

Not sure if this affects the setup - Check the option tab for the extension to enable stun

What does the activity log say about the device.

Check your backlist and remove any IP’s

 

[accentlogic]

I would highly recommend using an SBC for your connection to the cloud. Any Windows 10 computer can be used quickly to test it. If you don't have one to dedicate to it get a Raspberry Pi, or use the 3CX ISO to turn an old PC into a Debian SBC.

 

[Dennis Pillow]

The thing that makes me curious about this problem is that it does connect and has been working in the past. Yesterday it just deregistered and this problem has shown up.

 

[complex1]

Just for test, try next:
Replace your FQDN with the (static) WAN IP of the PBX.
Also make sure the W60B is running the latest firmware.

 

[Dennis Pillow]

This is what I am doing.


Steps for W60B Connection to 3CX STUN

• Setup W60B in 3CX “FXS/DECT” tab
• Configure extension in 3CX IE: 6201
• Factory default of W60B
• Copy STUN server link in 3CX FXS/DECT page for W60B
• Login to W60B local
• Paste link into SIP Server URL tab
• Click “Auto provision Now” button

No Phone is paired with W60B.

Question: Do I need to enter a User Name and Password on the Auto Provision Tab of the W60b Before hitting the auto provision button?

 

[complex1]

It's not necessarily to enter a User Name and Password, you may delete them.
You need to pair a handset

 

[Curtis C]

We had this exact same problem until yesterday at 2:16 p.m. The phone would register then go down repeatedly. So we did as Complex1 said we put in the ip of the pbx instead of fqdn and we went a little further and assigned the base unit a static ip. Almost 24 hours and phone has maintained registration. We hope this is the solution.Time will tell, but so far so good

 

[Dennis Pillow]

We had this exact same problem until yesterday at 2:16 p.m. The phone would register then go down repeatedly. So we did as Complex1 said we put in the ip of the pbx instead of fqdn and we went a little further and assigned the base unit a static ip. Almost 24 hours and phone has maintained registration. We hope this is the solution.Time will tell, but so far so good

how about a point of clarity? Are you talking about using the provisioning link for LOCAL LAN?
Did you use the http://xxx.xxx.xxx.xxx:5000

 

[Curtis C]

Login to W60B local
Accounts page Server Host 188.xxx.xxx.xxx (NOT FQDN) leave port 5060 at the bottom make sure NAT is enabled
Press confirm
Go to network tab of the phone. Tick use static ip and put in local lan iformation we made sure to use one of the last lan ports on the network 192.xxx.xxx.250 enter subnet/gateway. For DNS we used google.
Press confirm. Phone will need to reboot this took a solid 7 or 8 minutes.
Leave your provisioning url the same as on the provisioning page https:// xxx.xxx.xxx:5001
Not sure why this had to be done and I hope this helps. Ours has been up for well over 48 hours which is a new record this particular unit

 

[Dennis Pillow]

Login to W60B local
Accounts page Server Host 188.xxx.xxx.xxx (NOT FQDN) leave port 5060 at the bottom make sure NAT is enabled
Press confirm
Go to network tab of the phone. Tick use static ip and put in local lan iformation we made sure to use one of the last lan ports on the network 192.xxx.xxx.250 enter subnet/gateway. For DNS we used google.
Press confirm. Phone will need to reboot this took a solid 7 or 8 minutes.
Leave your provisioning url the same as on the provisioning page https:// xxx.xxx.xxx:5001
Not sure why this had to be done and I hope this helps. Ours has been up for well over 48 hours which is a new record this particular unit

I have messed with this long enough. I can only assume I have a defective unit. I think my next choice will be a Grandstream unit.

 

[accentlogic]

I have messed with this long enough. I can only assume I have a defective unit. I think my next choice will be a Grandstream unit.

If you are going to change cordless phone vendors the only other vendor with supported remote (STUN/SBC) DECT phones is snom. Grandsteam might work, but you will need to configure it them manually.

Either way, we only support remote DECT phones using an SBC at the remote site to avoid intermittent issues such as this. If the supported devices are on the same LAN as the 3CX SBC you get plug and play provisioning, elimination of firewall issues and your connection to the cloud PBX is encrypted. If there are no remote STUN phones the cloud firewall can limit SIP connections to only VoIP providers and 3CX servers (to pass firewall checks).

Whichever way you go, good luck.

 

[JohnS_3CX]

Hi Dennis,

Some additional points to check that I did not see you mentioned above:

- Did you check in case the WAN IP from which the Yealink connects has been blacklisted?

- Does your PBX pass the firewall checker?

- Did you uncheck "Disallow use of extension outside the LAN" on the assigned W60B extensions?

- Do you have the correct ports forwarded on the firewall behind which the Yealink sits?

- Did you check whether the firewall behind which the Yealink sits has SIP ALG and ensure to disable it?

 

[Dennis Pillow]

Hi Dennis,

Some additional points to check that I did not see you mentioned above:

- Did you check in case the WAN IP from which the Yealink connects has been blacklisted?

- Does your PBX pass the firewall checker?

- Did you uncheck "Disallow use of extension outside the LAN" on the assigned W60B extensions?

- Do you have the correct ports forwarded on the firewall behind which the Yealink sits?

- Did you check whether the firewall behind which the Yealink sits has SIP ALG and ensure to disable it?

I am using the Cloud 3CX system. It has been working fine until one day it just disconnected and will not hold a connection. I use the STUN service.

 

[Dennis Pillow]

I am using the Cloud 3CX system. It has been working fine until one day it just disconnected and will not hold a connection. I use the STUN service.

I can get it to register once and it just drops off and won't register again.

 

[JohnS_3CX]

Hi Dennis,

A couple of points:

1. This is beginning to sound like a classic firewall problem, with the ports closing after a while of inactivity. You should really check whether you have properly forwarded the ports of the W60B on the firewall/router/modem that sits in front of it. It's kind of an important requirement for STUN devices with regards to reliability and should be your first go-to.

2. The latest 3CX supported firmware is 77.83.0.20 - Ensure please that it is running this version. You can get it from here if needed. You must click "Software" on their page to see it.