Provision files 404

[ArcticLeaf]

Hi there,

I have a phone setup for my extension:


But when I try and auto provision my Yealink T46G, it just fails, with the log noting:

<134>May 17 16:39:42 LIBD[1184]: HTTP<6+info > Request Line: GET /provisioning/bXXXXXX/0XXXXXXd.cfg HTTP/1.1
<134>May 17 16:39:42 LIBD[1184]: HTTP<6+info > Host: XXXXXX.3cx.us
<134>May 17 16:39:42 LIBD[1184]: HTTP<6+info > User-Agent: Yealink SIP-T46G 28.82.0.20 00:XXXXXX:ed
<134>May 17 16:39:42 LIBD[1184]: HTTP<6+info > process response
<133>May 17 16:39:42 LIBD[1184]: HTTP<5+notice> response code: 404
<134>May 17 16:39:42 LIBD[1184]: HTTP<6+info > Chunked Encoding
<133>May 17 16:39:42 LIBD[1184]: HTTP<5+notice> response process finish!
<131>May 17 16:39:42 LIBD[1184]: HTTP<3+error > Client error, ret = 404
<131>May 17 16:39:42 ATP [1184]: ATP <3+error > https to file failed, code = 404, msg = Unknown Error, retry = 1
<132>May 17 16:39:42 ATP [1184]: ATP <4+warnin> Download mac.cfg fail
<134>May 17 16:39:42 ATP [1184]: ATP <6+info > Param err!
<134>May 17 16:39:42 ATP [1184]: ATP <6+info > send end provision!!

Furthermore, when I go to the URL https://XXXXXXX.3cx.us/provisioning/bXXXXXXXa/0XXXXXXXD.cfg directly in Chrome I get a 404.

I'm told in 3CX 15.x the files are generated on the fly. Further, I have removed and re-added the phone and have:

3CX Phone System Management Console ID: 10018
RPS request for Yealink T46 IP Phone of XXXXX (XX) delivered successfully


in my activity log. Is there something I'm missing/doing wrong?

 

[YiannisH_3CX]

Hello @ArcticLeaf

Please make sure that your FQDN resolves at the correct IP and that you can resolve it from the site the phone is located. Also make sure that https port 443 is open on the PBX side.

 

[ArcticLeaf]

Yep, my FQDN is fine [I can access the management console etc] and https is fully setup and working. Updating to 15.5 SP4 seemingly "fixed" it, albeit I'd like to know the root cause in case it's not actually fixed.

 

[YiannisH_3CX]

Updating to 15.5 SP4 seemingly "fixed" it, albeit I'd like to know the root cause in case it's not actually fixed.

You were able to provision the phone after you upgraded to SP4 without any additional changes?
The cause of the issue could be a number of things like the FQDN not resolving correctly or a blocked port on the firewall. Also there could be an issue with the configuration. Antivirus software can also cause problems with provisioning. Have you tried a different phone to make sure the issue has been resolved?