Yealink 46S not reprovisioning

[dashbrook]

I am trying to update the phone logo and clicking "reprovision" to get the phone to sync up rather than having to wait for 24 hours. The "reprovision" function is not working in v18 Update 4 build 965. I assume this is a bug? This function worked on prior builds.

 

[JohnS_3CX]

Hi @dashbrook

I removed your other post because I think we can address the rebooting and reprovisioning issues in a single post.

Please read the below post and provide us with more information. The more info we have, the better position we will be in to help out: https://www.3cx.com/community/threads/post-in-relevant-category.115838/

 

[dashbrook]

The system is running on Windows 2016 on-prem. The phones are running Yealink firmware 66.86.0.5 provisioned locally. The trunks are fine under Telnyx. No custom phone templates are being used. The firewall checker is fine.

We have several installations of this configuration on this build in separate offices. All behave the same way.

These functions used to work just fine on prior builds. I cannot tell you which build that was. Our systems started out on v16 and have been upgraded to this release over time.

 

[JohnS_3CX]

Ok if you are on-prem with locally provisioned phones and the reboot / reprovision command is not working you will have to choose a device to troubleshoot with. The feature worked on prior builds, but it also works on your current build and next.

I recommend factory resetting one phone (preferably a non critical one) and try to provision it from scratch:

1. Edit extension, delete the phone (and any other phone entries) and press OK
2. Edit extension again, ensure the phone is not there.
3. Factory reset the phone
4. It will appear as a bold New entry in your Phones tab which you can tick and assign to your extension.

Try this method and let us know if the phone starts to behave correctly after doing so. We will use this as an example to help troubleshoot the rest.

PS: Make sure you are using the latest version of Chrome, and don't use any browser plugins (ie. try in an incognito window) so we can rule out any browser based issues.