- 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
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.
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
- With manual provisioning, account1 can place/receive calls at the remote location.
- 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: