• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Trouble provisioning Yealink W52P V15.5

Status
Not open for further replies.

Stephen Hellriegel

Bronze Partner
Basic Certified
Joined
Jan 1, 2018
Messages
21
Reaction score
6
Similar to the closed thread started by Alex Mitton (post 240142) I am unable to get provisioning to work.

I have a functioning, fresh build V15.5 PRO Annual (15.5.13103.5 ) self hosted server.
I have a factory fresh W52P, I update the firmware on the handset and base to the latest from Yealink.
Base 25.81.0.10
Handset 26.81.0.30
  • I've followed the official guide: https://www.3cx.com/sip-phones/yealink-dect-w52p/
  • My firewall test is all green lights and happiness
  • Static IP, and using 3CX FQDN, my https is clean.
  • I built the Linux based PBX using the 3CX supplied debian 3CX .ISO image.
    • I have 3 other, larger systems, working fine with this image.
  • I reset the W52P to factory settings and tried again
  • I removed the extension from 3CX and added again
  • I went into the phone and under certificates, selected "Disable" for enforce certificates.
  • I removed the device from FXS/DECT section and added again
  • I am able to "pull" the MACid.cfg file from the PBX, on the LAN where the W52P is installed.
    • The provisioning URL returns the .cfg file at the remote LAN (and it looks plausible)
  • I am using Remote STUN configuration
  • I get certificate error exceptions (even with disable selected), in the Yealink phone log.
    • This happens when I go to the auto provision tab and click "auto provision now"
  • I can register the phone manually on account1 (and only account1)
    • With manual provisioning, account1 can place/receive calls at the remote location.
    • My manual provisioning prowess is insufficient to actually get the additional DECT extensions beyond the first to register with the 3CX PBX
My belief is simple: 3CX V15.5.13103.5 does not work with Yealink W52P DECT systems.
  • Perhaps the PBX is generating an invalid provisioning file?
  • Perhaps 3CX does not have the correct certificates loaded in the PBX image to allow the W52P to trust the PBX.

Anyone have a recipe to prove me wrong? I would really appreciate a wrench on the head, if it comes with directions.

-Steve

p.s.

Do not downgrade base station firmware 25.73.0.40 after upgrading to 25.81.0.10.
It will still work with the handsets, but the "phone" page, which has the firmware upgrade and auto provision options is broken; you hang the W52P. The only way out is to boot the unit up where you have a TFTP server at the well known address and a Yealink config file to force the upgrade.
 
Last edited:
Still working on this. Haven't unbricked my W52P base yet.

Yiannis, I notice that the CP860 firmware found on the 3CX website is newer than the "latest" firmware found on the yealink website for CP860. (And using the latest from Yealink for CP860 does not provision, using the official firmware from 3CX (newer than Yeaklinks Latest) works like a charm)

The documented procedure for setting up a Yealink DECT base is to use the "latest firmware" from the Yealink website. Based on the trouble I had with CP860 and with W52P, I suspect the "latest firmware" from Yealink is not the supported firmware I need to use.

I need to pull the firmware from the 3CX site so I know I am getting the firmware that 3CX has tested and guarantees.

Please add the official 3CX firmware files for supported DECT phones to:
https://www.3cx.com/support/phone-firmwares/

Thanks!
 
Follow up to be clear:
The link Yiannis pointed me to https://www.yealink.com/products_48.html
takes you to a spot on the Yealink page, where there is a download button, which presents a directory of a few special versions of firmware. These versions are newer than what you would find if you go to the phone via the yealink products menu and drill your way down to firmware.
So there are 3 places to look for firmware:
1) http://support.yealink.com/documentFront/forwardToDocumentFrontDisplayPage
2) https://www.3cx.com/support/phone-firmwares/
3) https://www.yealink.com/products_48.html

And for CP860, DECT phones, and T4XS, the firmwares on the 3 sites do not match. Hence my request that I only go to 3cx.com/support/phone-firmwares to locate the supported firmware to use 3cx. I wasted multiple hours trying to get things to work with the wrong firmware, simply because I was looking in the wrong "official" location!!!
 
  • Like
Reactions: DaleT
Hi,

I have running several W52P/W56P all with Base firmware 25.81.0.10 on v15.5 SP5.
All Bases are remote (STUN) and (auto)provisioned by 3CX.

My personal experience is that the Base can be downgrade to 25.73.0.40 without any issues, handsets can be downgraded also.

Before provisioning the Base first Reset it to Factory default, then fill the Server URL link with the value found in FXS/DECT Details e.g. “https://FQDN:5001/prov......cfg”, then set “Only Accept Trusted Certificates” to Disabled, press Confirm.
The Base reboot now and during the boot it will provisioned.

Hope this will help.
 
I can confirm the following:
1) Using the latest firmware from the Yealink product website (25.81.0.10) does not support 3CX
based on community feedback, this is due to certificate issues.
2) 3CX does not include the required firmware on their website, only an indirection to a special link of custom firmware at yealink.com.
3) Using the special firmware from the 3CX special firmware area on Yealink (25.81.0.30) works!
->I didn't have to do anything with the certificate settings!
firmware version 25.81.0.30 must include proper certificates, Yiannis can confirm or deny this.

I have provisioned via STUN and the phones are operational.
Hopefully, 3CX will add the DECT base/handset firmware to their own website of supported firmware to eliminate the guesswork of finding the correct image to load.

Anyone get transfers to work? I receive a call, hit transfer (get the groovy music), select one of the other handsets, and boom, just a busy signal.
 
Status
Not open for further replies.
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.