We have a 2 W52P bases, and 7 W52H handsets.
I initially set the time display to 12 hour clock format on all handsets. One of our employees asked me if I had done anything that would change it. I have not changed anything as far as I know. So I checked another handset near bye, and it too reverted to 24 hour format.
I have not checked all of them, but it appears they might all be reverting back to 24 hour format. Is there a way to force the time to 12 hour format?
It would be a nice feature to be able to set the time display as an option for each line in the web interface, because trying to track down each handset is a pain... especially if it is just going to revert back to 24 hour format anyway.
Hello Steve,
Does all the 7 handsets revert to 24 hour format, or just some?
Please check whether you have configured auto-provision (as below figure1).
The default time format can be defined by provision file (code as below figure2), if auto-provision working, phone will automatically update configuration in interval time. In other words, if it defined format as 24 hour, phone will revert it to 24 hours from 12 hours when provisioning even though you didn't change the time on handset manually.
thanks.
Peter
I have not configured auto provision; it should not do anything by default?
I keep forgetting to do a check in the afternoon, but I do know at least 3/7 (all connected to the same base) have reverted.
I will go and set them for 12 hour, and check again this afternoon.
Update 1:
At least two of the phones did not reset yesterday, after I make sure to set everything in auto provision to off / un-checked. Will check again today.
Update 2:
Sadly, the time was reset this afternoon again on at least one of them.
Hello Steve,
Sorry for my delay reply.
I seems strange to change automatically without any settings modified by anybody or AutoP. You mean all the faulty handsets are registered to the same base, in order to reproduce problem on my side phone, could you please tell me your base firmware and handsets firmwares? Highly appreciate if you can upload your config.bin file and your web UI login password if not for "admin"? And does it appear on handsets which registered to the other base?
BTW, have you reset the handset or base test when problem appeared?
Thanks in advance.
Peter
Listed on the "Phone" tab:
Firmware Version : 25.73.0.20
Hardware Version : 25.1.0.0.0.0.0
Rom file names:
25.73.0.20.rom
26.73.0.10.rom
I rebooted both base stations. I will go set the handsets to 12 hour this morning. See what happens this afternoon.
I have attached my auto-provision settings for reference.
Hi Steve,
How this issue going now?
Best Regards,
Peter
Seems like they are all doing this still. I haven't physically checked all hand sets, but 2-3 per base station. Both bases have the same thing happen to their handsets, using the same firmwares on both systems.
I reverted the password to 'admin' prior to exporting the config.bin.
I also attached the local.cfg, with the account data removed so you can see ntp settings and configs in that file.
(12-24-2014 04:07 AM)steve.ot Wrote: [ -> ]Seems like they are all doing this still. I haven't physically checked all hand sets, but 2-3 per base station. Both bases have the same thing happen to their handsets, using the same firmwares on both systems.
I reverted the password to 'admin' prior to exporting the config.bin.
I also attached the local.cfg, with the account data removed so you can see ntp settings and configs in that file.
Hello Steve,
Sorry for my late reply. We are trying to reproduce your issue under your config.bin file, maybe need some more time to figure out the result.
Any update, I'll let you know ASAP.
Thanks.
Regards,
Peter
Hi Steve,
We have reproduced out your problem and escalated to R&D evaluating. Any update, I'll tell you.
Thanks.
Regards,
Peter
(01-05-2015 09:58 AM)Yealink_Peter Wrote: [ -> ]Hi Steve,
We have reproduced out your problem and escalated to R&D evaluating. Any update, I'll tell you.
Thanks.
Regards,
Peter
Hi support,
why can't we have the option to set the time format on the web interface? why only thru provisioning or actual handset?