After updating the firmware on a T21P, auto provisioning now fails when trying to run it manually. The only time it works is when the phone powers up, successfully downloading all files and having no problems at all.
When I try and run a provisioning manually, either through the web interface or on the phone itself, nothing happens. The TFTP server shows no activity and the log files from the phone show:
Code:
<131>Sep 25 17:01:05 ATP [1312.1321]: DURL<3+error > [DCMN]download common error, errcode:68.
<131>Sep 25 17:01:05 ATP [1312.1321]: ATP <3+error > tftp to file failed, code = -168, msg = , retry = 1
<131>Sep 25 17:01:07 GUI [1296:1296]: APP <3+error > 667.766.538:from[app_vpPhone] sync[0] msg[396175][0][0] size[36] target[0xd2919e64] not found
The web ui also shows 'auto configuration failed'.
Not sure what's going on here or why provisioning only works on boot. Any tips?
(09-25-2020 04:13 PM)Snapdragons Wrote: [ -> ]After updating the firmware on a T21P, auto provisioning now fails when trying to run it manually. The only time it works is when the phone powers up, successfully downloading all files and having no problems at all.
When I try and run a provisioning manually, either through the web interface or on the phone itself, nothing happens. The TFTP server shows no activity and the log files from the phone show:
Code:
<131>Sep 25 17:01:05 ATP [1312.1321]: DURL<3+error > [DCMN]download common error, errcode:68.
<131>Sep 25 17:01:05 ATP [1312.1321]: ATP <3+error > tftp to file failed, code = -168, msg = , retry = 1
<131>Sep 25 17:01:07 GUI [1296:1296]: APP <3+error > 667.766.538:from[app_vpPhone] sync[0] msg[396175][0][0] size[36] target[0xd2919e64] not found
The web ui also shows 'auto configuration failed'.
Not sure what's going on here or why provisioning only works on boot. Any tips?
Dear Customer,
Thanks for reaching out and letting us know your question.
Base on your info, "tftp to file failed, code = -168, msg = , retry = 1", it means that the file doesn't exist or is forbidden to visit. So please kindly check your TFTP server first.
Thank you in advance.
Regards,
Jay
(09-28-2020 08:30 AM)Jay_Yealink Wrote: [ -> ]Dear Customer,
Thanks for reaching out and letting us know your question.
Base on your info, "tftp to file failed, code = -168, msg = , retry = 1", it means that the file doesn't exist or is forbidden to visit. So please kindly check your TFTP server first.
Thank you in advance.
Regards,
Jay
Hi Jay, thanks for your reply. So the TFTP server is all functioning as it should - in fact, I have two phones side by side, one still running 52.84.0.15 and the other I upgraded to 52.84.0.125. Both have identical provisioning settings.
The 0.15 one works fine, both on power up and manual provisioning. The 0.125 one provisions on power up, but when I manually provision, it immediately says ‘failed’.
The fact that it provisions successfully on power up suggests that the provisioning settings are all correct though.
I just tried downgrading to 84.0.90 and auto provisioning manually works as expected. Upgrading back to 0.125 gives me the ‘configuration update failed’ message every time when provisioning manually.
(09-28-2020 09:44 AM)Snapdragons Wrote: [ -> ] (09-28-2020 08:30 AM)Jay_Yealink Wrote: [ -> ]Dear Customer,
Thanks for reaching out and letting us know your question.
Base on your info, "tftp to file failed, code = -168, msg = , retry = 1", it means that the file doesn't exist or is forbidden to visit. So please kindly check your TFTP server first.
Thank you in advance.
Regards,
Jay
Hi Jay, thanks for your reply. So the TFTP server is all functioning as it should - in fact, I have two phones side by side, one still running 52.84.0.15 and the other I upgraded to 52.84.0.125. Both have identical provisioning settings.
The 0.15 one works fine, both on power up and manual provisioning. The 0.125 one provisions on power up, but when I manually provision, it immediately says ‘failed’.
The fact that it provisions successfully on power up suggests that the provisioning settings are all correct though.
I just tried downgrading to 84.0.90 and auto provisioning manually works as expected. Upgrading back to 0.125 gives me the ‘configuration update failed’ message every time when provisioning manually.
Hi,
Thanks for your feedback.
In this case, could you please follow the FAQ below to reproduce the issue and share the diagnostic files (pcap file, config.bin file and level 6 syslog file)?
> FAQ reference:
http://support.yealink.com/faq/faqInfo?id=707
If it is possible, please share with us these two phones' diagnostic files. Then I will be able to make a comparison between the issue one and the work-well one, and try to figure out what happened.
Thank you in advance.
Regards,
Jay