Re-provisioning Yealink W60B

[lilmunchkin]

Hello,
While deploying our phone system, I had created temporary user profiles. However, now, we have the permanent user profiles set up. I needed to update our handheld to reflect this update. However, the handheld just wouldn't update its line. I tried rebooting the handheld [W56H], the base unit [W60B]. I tried refreshing the 3cx FXS/DECT setup. And I even tried to just recreate the user extension. I ended up factory resetting both the base unit and handheld and decommissioning it from 3cx.

Which leads me to my current issue, I'm unable to re-provision the base unit on 3cx. It appears on the phone list but does not have an associated extension or an IP address listed. However, I know for a fact that the base unit has an IP address, as I can access the Yealink dashboard.

All of our phones are added via SBC.And I've been using the following instructions to provision our handheld phone.

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

I have no idea what I'm doing wrong or what could possibly be the issue.

 

[Saqqara]

Have you tried to manually adding the provisioning url into the base unit

 

[lilmunchkin]

If you're referring to going to the Yealink configuration into Settings -> Auto Provisioning -> adding the server url, yes, I've tried that multiple times.

 

[JohnS_3CX]

Before you try provisioning, have you read the part of the guide that helps you to update to the latest firmware?
https://www.3cx.com/sip-phones/firmware-upgrade-yealink-dect-w52p/

You should end up with:
W60B v77.85.0.25
W56H v61.85.0.35

 

[lilmunchkin]

I can confirm that both the base unit and the handset have the latest firmware.

 

[JohnS_3CX]

Hello,

SBC provisioning relies on TLS connections working correctly. The provisioning file is downloaded by the W60 from the PBX over the internet. These are the main things needed so that the W60B can connect to your PBX and provision itself:

- Are you using a custom FQDN + certificates by any chance?

- Is there a valid NTP server on your network or are you perhaps blocking NTP?

- Is the local DNS server resolving the FQDN in our provisioning link correctly?

- Could there be some strict firewall rules preventing communication?

 

[lilmunchkin]

I'm unsure if any of those reasons could be the cause of a failed provisioning, especially since the base unit was previously provisioned using the same setup.

 

[JohnS_3CX]

Assuming that the config in the FXS/DECT page of 3CX is correct, there really is not much reason for provisioning to be failing. If you want to be sure, click the provisioning link from a PC on the same network as the W60 and see if your config file can be downloaded off 3CX from that location.

If the answer is yes, then please refer to the aforementioned points and tells us about them so we can get to the answer by process of elimination.