T54W Router Phone provisioning fails - provisioning URL returns 404

[julienknowsmuch]

Hi all,


I'm setting up a fresh 3CX SMB Cloud instance with a Yealink T54W as router phone and several T46S as regular extensions behind it.


What I've done so far:

• Updated the T54W to the correct 3CX-supported firmware (96.87.0.22)
• Updated all three T46S phones to 66.86.0.180 (had to go through an intermediate version 66.84.0.35 first due to the old firmware issue)
• Added the T54W in the Web Client under Admin > Voice & Chat > Users > IP Phone tab, selecting "Router Phone", with the correct MAC address
• Copied the generated provisioning URL and entered it manually on the phone (Server URL field), with DHCP Active off since option 66 isn't configured
• Pressed "Auto Provision Now" - nothing happens, no error shown, no reboot

The actual problem:
When I open the exact provisioning URL 3CX generated (e.g. https://[myFQDN].3cx.cloud/provisioning/

) directly in a browser from a PC on the same network, I get an HTTP 404 error saying the page cannot be found - even though the FQDN itself is reachable.


I've already:


[LIST]
[*]Deleted the phone from the extension and re-added it as Router Phone (new URL generated) - same 404
[*]Confirmed the URL I'm testing matches exactly what's shown in the Web Client
[*]Confirmed I'm not currently IP blacklisted (I can log into the Web Client fine)
[/LIST]

[B]My question:[/B]
What should I check in the Web Client to troubleshoot this further? Is there a step in the Router Phone setup I might be missing (e.g. a "Confirm"/"Save" step that isn't sticking), or could this be a backend issue with how the provisioning link is generated on SMB Cloud?


Any help would be appreciated - happy to provide FQDN/screenshots via DM if needed.


Thanks!

 

[Claas Felix Beyersdorf]

Maybe you only haven't written it and tried the right one but you have to use:

https://[myFQDN].3cx.cloud/provisioning/MACADDRESS.cfg

If you haven't enable secure provisioning which would make it more difficult.

I would suggest you to download the file to your computer and upload it to the phone.
If nothing is blocking RPS normally this should not be necessary.

But e.g. if you have a firewall which makes TLS inspection this would block the phone from downloading its config. As the Firewall would break the HTTPS connection generating a certificate with a CA non of the phones trust.

So first ensure you can download the file by yourself via browser. If this works upload the config to the phone if it isn't working also, you know there is something blocking the provisioning of the phones.

One last thing. I'm not entirely sure if my informations are correct, but I think SMB won't support Hardware phones anymore? But as you were able to create them via the GUI I might be wrong or you did this not with an SMB? Even though you posted in SMB forum?