DST a week early

[Alphabetic]

Good morning,

we've got 2 instances (that im aware of atm) running 18.0 U9 B20

The phones have gone in to BST a week early.

The time on the OS is the correct time, using yealinks on the latest supported FW with supported template.

 

[telica]

@telica
We haven't had any report for Fanvil devices so far and if you do have an issue, feel free to open the ticket for review or provide more detailed information on the issue here.

The customer that reported this has Fanvil X4 and X5's. I will investigate the settings further and post findings.

 

[Lee Cramman]

It beats me how this is a leap year problem - there are the same number of days in March every year...

Next year isn't a leap year and it's going to happen again then (without a fix).

 

[daniel.marsh]

It beats me how this is a leap year problem - there are the same number of days in March every year...

Next year isn't a leap year and it's going to happen again then (without a fix).

the setting sets March to "4th Week" instead of "Last Week" unlike October, which is set to "Last Week"

 

[OlegR_3CX]

@telica
X5 is the end of life.
For the X4, just ensure you are using the default template, and latest firmware and reprovision the phones.

 

[JohnS_3CX]

The customer that reported this has Fanvil X4 and X5's. I will investigate the settings further and post findings.

Only check X4U and X4U-V2 both of which appear to have the correct time as of this post (tested region United Kingdom London for reference).

The EOL phones can no longer be provisioned unless you do it manually, in which case you must also manage DST manually.

 

[telica]

@telica
We haven't had any report for Fanvil devices so far and if you do have an issue, feel free to open the ticket for review or provide more detailed information on the issue here.

The user in question is using Fanvil X4 and X5 handsets.

 

[telica]

@telica
X5 is the end of life.
For the X4, just ensure you are using the default template, and latest firmware and reprovision the phones.

Yep, for the X4's I've checked the UI on the phone and it's using "Last week", so I've asked the customer to confirm it's just the X5's as these phones don't have a "Last week" option, just the week numbers - so these will likely be the affected handsets.

And as you say they're EOL anyway!

 

[OlegR_3CX]

@telica Thank you for the update and feedback provided.
See also the comment of @JohnS_3CX regarding X4 phones.

 

[onix]

Hi guys.
Apologies for the inconvenience this caused.
This is a Yealink issue caused by this year 2024 being a leap year. (So March now has 5 weeks, not 4)
Yealink firmware thinks March has 4 weeks.
We have escalated this issue to Yealink with top Priority and will keep you posted.
Once again, on behalf of the teams involved, I apologize for the inconvenience caused.

2025 and 2026 will be not a leap year, but March will have 5 Sundays too !

 

[Alphabetic]

Can 3CX not modify the default template with new parameters? would this be quicker then waiting for Yealink? 3 days in now and it doesnt seem like much is happening.

 

[JulienI]

Hi,

created custom template with the settings below, works fine for instances not hosted by 3CX (no custom templates), but anyway it takes a lot of time, and I'll have to revert to default templates once fixed. I also would have loved a template hotfix pushed by 3CX, instead of waiting for an updated firmware which can have side effects due to the lack of time to test it properly.

local_time.summer_time = 1
local_time.dst_time_type = 1
local_time.start_time = %%param::time_dst_start_month%%/5/7/%%param::time_dst_start_hour%%
local_time.end_time =  %%param::time_dst_end_month%%/5/7/%%param::time_dst_end_hour%%

 

[EBrooke]

It's ridiculous that Yealink's response to a widespread issue such as this seems to be radio silence.

 

[Learning Academies Trust]

@

Thank you for the feedback provided here.
As we have mentioned above a few times, the issue is in the actual firmware, as the template is using automatic settings which do not work.
Indeed you can find a workaround and do manual changes, however, this is not what we wish to do, as this could potentially require you to do the template update once in a while.
I know that it can be annoying, however, we are awaiting feedback and possible solutions from the vendor.

I can confirm from our experience there is nothing wrong with the existing firmware and we're using 96.86.0.77 for our T53W and 66.86.0.15 for our T42S. If you manually change the template to the correct settings and reprovision it, the existing firmware works as expected.

As I mentioned above the current default 3CX template sets it to start DST on the "4th week", not the "last week". If you manually download the phone provisioning profile .cfg it has the wrong configuration being sent to the phone from the 3CX server.

 

[daniel.marsh]

I can confirm from our experience there is nothing wrong with the existing firmware and we're using 96.86.0.77 for our T53W and 66.86.0.15 for our T42S. If you manually change the template to the correct settings and reprovision it, the existing firmware works as expected.

As I mentioned above the current default 3CX template sets it to start DST on the "4th week", not the "last week". If you manually download the phone provisioning profile .cfg it has the wrong configuration being sent to the phone from the 3CX server.

How did you manually change the template? I've been going onto the UI of all my phones to update the time & date DST settings to "Enabled" and "Last Week" instead of "Automatic"

 

[EBrooke]

We've just left ours alone and told people that the time's wrong. It's probably caught people out here and there, but in my opinion it isn't worth the effort given the time will be correct again as of Sunday and Yealink will hopefully issue a firmware fix soon after

 

[OlegR_3CX]

Hi guys.
We did have an update from Yealink and were informed that the issue will be corrected in their next firmware update.

 

[Lee Cramman]

Hi guys.
We did have an update from Yealink and were informed that the issue will be corrected in their next firmware update.

Did they give an ETA?

 

[EBrooke]

I filed a bug report with Yealink also and received the following response:

Hi Team,

Hope you are doing great

We are already aware of this.

This is a phone bug.

Two solutions:
1. For single units:
Method 1: Configure the correct time manually:
Step 1: Access the Yealink device’s website
Step 2: Go to setting-> Time & Date
Step 3: Change the Daylight Saving time Automatic -> Enable
Step 4: Change the Fourth week to Last week.

2. For batch modify:
Configure several devices by auto provisioning:
1. Download the correct Default Summer Time configuration file via this link: https://fileonline.yealink.com/?ShareToken=07590280313B52AABC67E52E0CE58A54BEA279C0
2. Add parameter to the cfg provision file: auto_dst.url = [http://%3Cserver/]http://<server IP address>/AutoDST.xml
Then upload the configuration file to the server, and get the auto-provisioning URL
3. Access to the device’s website->Setting->Auto provisioning->Fill the Auto provisioning URL with correct information.
4. Press the Auto provision now

Meanwhile, we will fix DST solution in the next firmware version and release in the Yealink (supportyealink.com) website. Please noted.

You can also wait till Sunday and UK time will change.
Then we will release new firmware soon, so that you can manage a time to upgrade all.


Regards,

 

[Drachengrube]

Hey,

I wanted to ask if anyone got that problem solved without tinkering? I've contacted Yealink support but they are telling me, the wrong time/DST config is coming from the 3CX PBX which I can't confirm.

Regards

 

[Lee Cramman]

Hey,

I wanted to ask if anyone got that problem solved without tinkering? I've contacted Yealink support but they are telling me, the wrong time/DST config is coming from the 3CX PBX which I can't confirm.

Regards

Sounds like a fob-off from support - the problem is proven to be a Yealink one.