Yealink W52 Provisioning problems.

[DylanXtremeP]

Hi all, having a hard time getting W52P's to work with our 3XC server.
Rest of T23G's work fine at multiple sites, including where the W52P is.

I've upgraded the Firmware as per: https://www.3cx.com/community/threads/trouble-provisioning-yealink-w52p-v15-5.58569/
Settings done as per: https://www.3cx.com/sip-phones/manually-provision-yealink-dect/ & https://www.3cx.com/sip-phones/yealink-dect-w52p/#h.dj8kxtpzsixe

Error logs from phone are:
<131>Jan 9 02:07:32 LIBD[1283]: HTTP<3+error > Client error, ret = 404
<131>Jan 9 02:07:32 ATP [1283]: ATP <3+error > http to file failed, code = 404, msg = Unknown Error.

3CX ver: 15.5.15502.6

Both types of phones generate these Cisco Firewall logs:

1 2019-01-9 12:20:45 AM alert dhcpd: received INFORM from 00:15:65:fa:ee:47
2 2019-01-9 12:20:42 AM alert dhcpd: received INFORM from 00:15:65:fa:ee:47
3 2019-01-9 12:20:33 AM alert dhcpd: received REQUEST from 00:15:65:fa:ee:47
4 2019-01-9 12:20:33 AM alert dhcpd: received DISCOVER from 00:15:65:fa:ee:47
5 2019-01-9 12:20:22 AM warn lldpd[26925]: some mandatory tlv are missing for frame received on br0

Made sure to follow these steps: https://www.3cx.com/community/threa...-removed-yealink-sip-w52p-provisioning.46629/
and made sure ' Disallow use of extension outside the LAN' un-ticked.

After doing Auto-Provision on W52P interface, have to powercycle phone, always shows as 'Provisioing Failed' on handset, and Ext in 3CX shows as red.
Full logs and phone config attached.
Please advise.

 

[eddv123]

If you are setting these up using the remote STUN method SIP and RTP ports are incremented per handset (see under the provisioning tab): https://www.3cx.com/docs/ports/

This can make using multiple "STUN" handsets on a remote site a bit messy, as per: https://www.3cx.com/docs/manual/configuring-ip-phones/

"for sites with 1 or 2 IP phones where a local SBC is overkill"

Despite this is does sound like a provisioning issues, and if T23G's work then it is specific to the DECT phones (not the provisioning port or connection to the redirection server etc).

If you are running the method from the guide (manual input of the provisioning link in the phone) and this still is not working, you could un-check the setting "Allow trusted certificates only" under the security section of the base station. This used to be an issue you would get with the standard desk phones - worth a look.

Failing that you will need to acquire the full log and PCAP the base as per: http://forum.yealink.com/forum/showthread.php?tid=1319

 

[DylanXtremeP]

I've tried Local, and Remote Stun setup methods. Also, there is currently only one DECT phone plugged in at all.

Un-checked "Allow trusted certificates only", had no difference.

Generated and attached logs.

 

[cobaltit]

So 404 means file not found. Disallow outside of LAN has no bearing on provisioning. A typo in the MAC address perhaps? I would confirm you can manually download the config via browser first and then go from there. If that works but the provisioning doesn't try unchecking the PCI/SSL box in 3CX.

 

[DylanXtremeP]

Thanks Cobalit.
I have re-added the MAC address as suggested, no change, see attached screenshot.

I went to grab the config file as per https://www.3cx.com/blog/docs/v15-finding-provisioning-files/, but the Dect phone not in the list, W52P was not available to add, see screenshot.

 

[Saqqara]

You do not add the w52p to the extension

You add the dect base unit to fxs/dect config - which you have done. After doing this edit the config and add the extension numbers to the extension tab

This link may help you more https://www.3cx.com/sip-phones/manually-provision-yealink-dect/

Have you tried manually adding the provisioning url into the dect base unit web front end

Make sure the IP address has not been blacklisted

 

[Saqqara]

What is the network setup ?

Are the phones on the same local network ?

If remote are you trying to use SBC or STUN. If stun how many other phones on the same remote network

 

[YiannisH_3CX]

While in the 3CX management console navigate to FXS/Dect and select and Edit the Yealink dect device. In that page you should find the provisioning link for the base.
Copy that link and paste it to a browser that is located in the same LAN as the Yealink Dect device. Can you download the config file?

 

[DylanXtremeP]

Hi Saqqara,
I believe I already have done that, please see attached screenshotsView attachment 9341 View attachment 9342 View attachment 9343

Both phones are on a local switch with a Fibre link to the 3CX server, with I understand is a VM on the client's Azure cloud.
The T26G desktop phones work fine here and at the client's site.
I have used Remote Stun setup, no change. At this site, we have one T26G (to compare and test with) and the one W52P

 

[DylanXtremeP]

Hi Yiannish,
I was able to download the config file.
I logged into the W52P and imported the file. (Settings -> Configuration)
Powercycled base of W52P, able to make an outbound call!

Now I am left with the questions;
Why can we not auto-provision the phone?
Will we have issues when we setup multiple W52P's at the client's site?

I highly appreciate the help so far, and I hope you can assist further.

 

[Saqqara]

Where you have assigned the same extension to all the 5 extension slots, what happens if you only enter ext 2260 in the first extension and leave the rest blank

I would factory reset the base unit and try entering the provisioning url manually again

 

[YiannisH_3CX]

Glad to see you got it working. However the screenshots you posted make your system extremely vulnerable to hacking so i deleted them. Please be more careful with what you post in the future in public forums.