DST change

[Alphabetic]

Hi all

were at that time of year again where the clocks change but the time on the phones dont.

are we waiting for a new template?

 

[KoesioOccitanieTech]

Hello,

Same problem here, that was already a thing last year.

In Yealink template, the summer time is set to the "4th sunday of the month" instead of the "last sunday of the month", resulting of a time switch early when there is 5 weeks in march.

Post in thread 'DST a week early'

Mar 25, 2024

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.

• OlegR_3CX

• 

I don't know why this isn't fix yet by 3CX and Yealink.

 

[Alphabetic]

I looked at flicking this to 1 but it made no difference

 

[noord]

Hello,

Same problem here, that was already a thing last year.

In Yealink template, the summer time is set to the "4th sunday of the month" instead of the "last sunday of the month", resulting of a time switch early when there is 5 weeks in march.

Post in thread 'DST a week early'

Mar 25, 2024

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.

• OlegR_3CX

• 

I don't know why this isn't fix yet by 3CX and Yealink.

They thought it was caused by the leap year and because of that, they thought they'd have at least 4 years to fix the issue.

But it has nothing to do with a leap year, it just depends on the number of Sundays in March (and therefore it should be set to 'Last Sunday of March')

 

[krieg-it]

Same issue here for germany, implementing this fix in the templates for Yealink phones at least resolves the issue for now.

Post in thread 'DST a week early'

Mar 26, 2024

Is there a solution for the problem with Yealink phones?

You can make following changes in the Phone template

local_time.summer_time = 1
local_time.dst_time_type = 1
local_time.start_time = 3/5/7/2
local_time.end_time =  10/5/7/2

Though you then have to reconfigure the templates on all the phones.
I'd advise the customers to just sit this one out. Not worth the work needed.

• SSO

• 

 

[Mark_M]

Hopefully this can be resolved quickly!

 

[KoesioOccitanieTech]

They thought it was caused by the leap year and because of that, they thought they'd have at least 4 years to fix the issue.

But it has nothing to do with a leap year, it just depends on the number of Sundays in March (and therefore it should be set to 'Last Sunday of March')

Yep, not a leap year thing.
If it's not fix again, 2026 will be the same because there is 5 weeks again in march.

 

[JoshWS]

Our Phones in the UK are showing GMT +1 currently when the clocks don't change until next Sunday.

 

[jon_a_w]

Still can't believe this isn't fixed after it was said it would be last year...

Amending the templates will work, but it's a pain in the...

You can temporarily get round this issue by changing the office hours location to 'Atlantic / Reykjavik' for the week and then swap back Monday as they don't observe DST.

 

[fxbastler]

One way to set this automatically for a 3CX is a Powershell script, as described here

https://www.3cx.de/forum/threads/yealink-uhrzeit-falsch-sommerzeit-eine-woche-zu-früh.118874/post-447103

Don't forget to reset it next week

 

[yules67]

Yealink have fixed the bug on the last firmware released in February. Now 3CX need to released their updated version too.

https://support.yealink.com/en/portal/knowledge/show?id=67763cf0d3e9b211da6b5197

 

[Lee Cramman]

Yealink appear to have published more up-to-date firmware under the heading "3CX Solution" - https://www.yealink.com/en/solution-detail/resource-for-3cx

It's mentioned on the German forum that Yealink have said it's a fix but I've not seen a successful test.

I wouldn't want to put unsupported firmware on our phones so it would be good to hear from 3CX as to whether this is just waiting to go through testing in order to be released, or if I am barking up the wrong tree.

 

[Lee Cramman]

Yealink have fixed the bug on the last firmware released in February. Now 3CX need to released their updated version too.

https://support.yealink.com/en/portal/knowledge/show?id=67763cf0d3e9b211da6b5197

Just beat me to the punch

 

[Alphabetic]

I pushed this FW to my phone and the time is still out.

 

[SteveITS]

, it just depends on the number of Sundays in March (and therefore it should be set to 'Last Sunday of March')

Total aside from the thread but many years ago we standardized on using full Friday backups (this was in the tape days). The fifth would also function as an occasional long term backup. We had quite a few clients question how there could be five Fridays in a month.

 

[fxbastler]

Total aside from the thread but many years ago we standardized on using full Friday backups (this was in the tape days).

We often did that and we still do it today but we've always used Thursday for that. This way, the long-term backup leaves the company Fridays (before the weekend). Yes, we use at least nine media: five for Thursdays and four for the rest of the week.

 

[zeeb]

crosslink to the german section: https://www.3cx.de/forum/threads/ye...merzeit-eine-woche-zu-früh.118874/post-447148

The issue is resolved by updating the firmware to 96.86.0.118 and then to 96.87.0.16 and performing a factory reset of the phone.
The firmware update alone does not fix the problem.


Is there any known method to automate both steps?

 

[Alphabetic]

crosslink to the german section: https://www.3cx.de/forum/threads/yealink-uhrzeit-falsch-sommerzeit-eine-woche-zu-früh.118874/post-447148

The issue is resolved by updating the firmware to 96.86.0.118 and then to 96.87.0.16 and performing a factory reset of the phone.
The firmware update alone does not fix the problem.


Is there any known method to automate both steps?

I hope this aint the official solution cos I dont fancy factory resetting a load of phones

 

[templeben]

Still can't believe this isn't fixed after it was said it would be last year...

Amending the templates will work, but it's a pain in the...

You can temporarily get round this issue by changing the office hours location to 'Atlantic / Reykjavik' for the week and then swap back Monday as they don't observe DST.

Just to say, this didn't work for us.Whilst the phone picked up the timezone change, it didn't disable the DST setting which was set to London/UK setting. We could set our timezone to somewhere -1 but this will affect logs and voicemail etc.

 

[Recnats]

Interesting that this happened last year as well and still no fix in place. Shocking!

We will put up with users complaining about the time for the next few days unless a fix is released before then. To me, Yealink is at fault here, if the timezone is set correctly and DST is set to automatic, it should follow the rules of said timezone. Only fix for this can be a firmware update from Yealink and subsequently approved by 3CX once tested