Yealink T54W provisioning but not registering

[GTAYLORST]

I have a T54W with 96.86.0.74 firmware set up as a local phone on a 18.0 (Build 939) server. It provisions, but it fails to register. I have deleted the phone multiple times and factory reset the phone multiple times. I have tried both through the web client and the master PBX interface. It is provisioned to an extension, but when you pull up the phone list it shows as a new phone and refuses to be assigned to an extension. I even set it up as a SBC phone only to have it fail to register. In that case it provisioned and the server said the SBC was up, yet the phone still failed to register. I am looking for any help solving this. Let me know what other information is needed solve this.

 

[Charles_3CX]

You mention that you are setting up the IP phone locally to the 3CX system, but mention 3CX SBCs, which you do not use for locally provisioned IP phones.

If you have set this phone to a router phone, then you have registered it with RPS, and now, every time the phone reboots, you will contact the vendor's RPS to try to pull down the configuration.

Try to first update the firmware to 96.86.0.76 as per this guide: https://www.3cx.com/docs/phone-firmwares/

Add the phone to the extension via the management console and specify the MAC address settings, setting it as locally provisioned, then copy the provisioning link, access the IP phone web interface, and paste the link under the phone's provisioning server URL section, press confirm and auto-provision to force the IP phone to provision locally.

 

[GTAYLORST]

Solved. The problem turned out to be because of how this system is setup it was three interfaces. One showing up as its URL, One as its outside IP, and then the inside IP. Apparently it defaults new phones to the URL even for Inside phones, no matter if it is programmed from the web client or the management interface. As soon as I set the phone to the internal IP of the local interface it registered just fine. Thank you for your answer as it led me think about checking where it was pointing the phone.

 

[SteveITS]

Apparently it defaults new phones to the URL

This is how 3CX will operate going forward:
https://www.3cx.com/docs/creating-fqdn-split-dns/