Solved Yealink phone won't auto-provision

[c.holloway]

Good afternoon.

I'm running into an issue with a single T42S Yealink phone that will not auto-provision from their 3CX server after a factory reset. This phone is on the same local lan as the 3CX server in question and and from what I can tell other phones on the same LAN work just fine (I don't have another phone that can be down during production so I haven't factory reset anything else. But they all previously auto-provisioned and I believe this one never has)

When I navigate to the url http://x.x.x.x:5000/provisioning/hash/mac.cfg I do NOT get a file generated from nginx. I have deleted and recreated the extension and still do not receive the file when navigating to the url. I can only presume this phone isn't auto-provisioning because nginx isn't serving up the file. I've restarted the nginx service with no success. I would appreciate any guidance you can provide

 

[Saqqara]

What version of 3CX are you running ?

Couple of things to do / check

Is the phone running the correct firmware -
https://www.3cx.com/support/phone-firmwares/

After factory reset, does the phone appear in bold text within 3CX Management console with Phones tab

Once you add the phone to an extension you should get a provisioning link under the phone provisioning tab. Make sure that the link contains the correct IP and provisioning folder

What happens if you manually add the provisioning url into the web gui of the phone - Settings - Auto Provision - Server URL field.

Does any of the logs explain what is going on.

Is the phone IP address blacklisted within 3CX

 

[c.holloway]

Once you add the phone to an extension you should get a provisioning link under the phone provisioning tab. Make sure that the link contains the correct IP and provisioning folder

The IP and the rest of the URL is correct.

What happens if you manually add the provisioning url into the web gui of the phone - Settings - Auto Provision - Server URL field.

Nothing much. The phone says "Configuration updating..." for approximately 2 seconds then gives an "Operation Complete!" and then does nothing further.

Does any of the logs explain what is going on.

The 3CX server doesn't show any attempt from the phone to register. I'm not getting any errors that explain why this isn't working.

Is the phone IP address blacklisted within 3CX

It is not blacklisted in the MC

 

[giwm]

Are you using a custom template? If so, try using a standard 3CX template and see if it provisions. Also, firmware as mentioned is important.

 

[YiannisH_3CX]

Hello @c.holloway

Try downloading a config file for a different phone. Does that work? Also if you add a BLF key to an already provisioned phone and re-provision it does that work?
What is the IP range the phones and server are using?

 

[c.holloway]

I can download the config for some phones but not others. All the phones I've tested on are currently registered and at one point provisioned properly.

If I apply a new BLF key to one of the phones that the system will actually generate a config file for, it will update just fine. In testing I have come across a few other phones that don't seem to get their files generated and these phones also will not provision.

The phones and the server are both on the 10.10.1.X/24 network. Auto-provision fails using both DNS name and the IP address of 10.10.1.10 (3CX)

 

[c.holloway]

Are you using a custom template? If so, try using a standard 3CX template and see if it provisions. Also, firmware as mentioned is important.

Using a standard template for T42S

Currently 3CX is a few service packs behind so I plan to update this to the latest version after production. It is difficult to say if the phone is running supported firmware for the current service pack as the upgrade firmware option on the Phones page only references the latest supported for SP5. I CAN say that both phones that work and phones that do not are running the same firmware so that doesn't seem to be the issue.

I have since restarted services in 3CX with no effect, some provisioning files simply aren't being created. My current hope is that updating to the latest service pack will iron this out, I will report back after I update this evening.

 

[c.holloway]

The service pack updates resolved the issue. When in doubt, check the obvious. Thanks everyone.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution