[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers.
You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020
How to upgrade Handset fw 26.30.0.50 in remote mode without usb tool?
Dear Staff,
is it possible to upgrade the WP52H via remote mode (i.e. firmware.url in file config),
instead of using usb tool?
Thanks for support
Regards Walter
RE: How to upgrade Handset fw 26.30.0.50 in remote mode without usb tool?
I have just upgraded my base to 25.30.0.50 and would like to do the same with my 2 handsets. I heard a comment that the updated base will push the handset firmware to the handset overnight via wifi but cannot find any documentation to substantiate this. Is this correct or is the USB tool the only option to upgrade from 26.30.0.10 to .50? Many thanks
RE: How to upgrade Handset fw 26.30.0.50 in remote mode without usb tool?
Hi Bucklebery,
The wifi upgrade technique is in progress but we still don't know how to use it. So it only can update W52H using usb tool now.
If the technique is released, we will blast to you.
(This post was last modified: 10-30-2013 04:51 PM by Yealink Support.)
RE: How to upgrade Handset fw 26.30.0.50 in remote mode without usb tool?
(10-30-2013 04:49 PM)Yealink Support Wrote: Hi Bucklebery,
The wifi upgrade technique is in progress but we still don't know how to use it. So it only can update W52H using usb tool now.
If the technique is released, we will blast to you.
I have now upgraded both the base and the handsets however the daylight saving is still showing 1 hour earlier. Do I need to do anything else as your documentation shows " Bug #10. Fixed the issue that ‘Daylight Saving Time’ doesn’t work when set to ‘Automatic’, and the handset’s time is an hour earlier."
Should I restart the base or reregister the handsets? Cheers
RE: How to upgrade Handset fw 26.30.0.50 in remote mode without usb tool?
Hi Bucklebery,
Could you try to reset to factory and reboot again?
Do you double check the version of handset and base?
If yes, please kindly supply us Syslog level 6, config.bin and trace.
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
RE: How to upgrade Handset fw 26.30.0.50 in remote mode without usb tool?
[attachment=413][attachment=414]
(10-31-2013 08:50 AM)Yealink Support Wrote: Hi Bucklebery,
Could you try to reset to factory and reboot again?
Do you double check the version of handset and base?
If yes, please kindly supply us Syslog level 6, config.bin and trace.
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
Config.bin will be in next post as it wouldn't upload
(10-31-2013 08:50 AM)Yealink Support Wrote: Hi Bucklebery,
Could you try to reset to factory and reboot again?
Do you double check the version of handset and base?
If yes, please kindly supply us Syslog level 6, config.bin and trace.
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
I had to rename it .txt as .bin would not upload - "Error that type of file not allowed" What hours do you work?
(This post was last modified: 10-31-2013 07:05 PM by Bucklebery.)
RE: How to upgrade Handset fw 26.30.0.50 in remote mode without usb tool?
Hi Bucklebery,
Thanks for your files. We have found the issue. It is a DST time issue only for +12 New Zealand(Wellington,Auckland) .
I have submitted your issue to our R&D and they will fix it.
If any update, i will contact you soon.