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.

 

[Alphabetic]

Phone config is correct

 

[VoiceKing Support]

Same issue here in Belgium, 3CX clients and other asterisk based systems have this issue.
So think it's a global problem, not related to 3CX.

 

[KoesioOccitanie]

Same issue in France, automatic is for the "4th week" instead of "the last" sunday.
Maybe firmware issue ?

 

[Alphabetic]

ah yes, there are 5 sundays in March this year, this explains it. Need a new template pushed out

 

[KoesioOccitanie]

ah yes, there are 5 sundays in March this year, this explains it. Need a new template pushed out

There will be 5 sunday until 2027 in march. So yeah... This will be a thing for 2 more year if they don't nothing about it.

 

[support-techit]

Hello,

As some have already stated it seems related to the fourth Week parameter :



However, all model are not affected , our T46G does not have the issues and are correctly fixed on the last Week :



Hope a firmware fix will be released.

 

[JamieLewisIBT]

Just for some clarity, is this effecting the handset only not call routing on 3CX?

 

[Alphabetic]

just the time displayed on the handsets

 

[MattKime]

Same issue on all Yealinks!!

 

[EBrooke]

I am also having this problem. May be best to follow this on Yealink's forums as it's not a 3CX issue?
I can see someone has opened a thread on Yealink's forums. I don't know if it's allowed to link to it from here so I won't.

 

[VoiceKing Support]

http://forum.yealink.com/forum/showthread.php?tid=47542&pid=75613#pid75613

 

[OlegR_3CX]

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.

 

[telica]

We believe this is also affecting Fanvil handsets.

 

[Learning Academies Trust]

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.

Hi OlegR,

I've found the issue in the 3CX provisioning template and the user 'SSO' pointed out the same thing here https://www.3cx.com/community/threads/yealink-dst-broken-summertime-already-set.125990/#post-595030

The following config is set in yealinkT4x.ph.xml and yealinkT5x.ph.xml files
local_time.dst_time_type = 0
local_time.start_time = %%param::time_dst_start_month%%/%%param::time_dst_start_day%%/%%param::time_dst_start_hour%%
Currently it is set to local_time.start_time = 3/28/2 by default.

You need to change 0 to 1 so that the template follows 1 - By Week instead of 0 - By Date
local_time.dst_time_type = 1

Additionally the start time needs to not be the 3=March / 28=28th / 2=02:00am
local_time.start_time = 3/28/2

Instead it should show 3=March / 5=Last Week / 7=Sunday / 1:0=01.00am
local_time.start_time = 3/5/7/1:0

It might be worth making two parameter in 3CX template e.g. time_type and start_time instead of separating the start_month, start_day, start_hour? e.g.
local_time.dst_time_type = %%param::time_dst_time_type%%
local_time.start_time = %%param::time_dst_start_time%%

Hope that helps you for correcting/adjusting the template going forward.

Thanks,
Luke

 

[OlegR_3CX]

@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.

 

[Yanis Belbagra]

Is there a solution for the problem with Yealink phones?

 

[SSO]

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.

 

[TheodorosG_3CX]

Besides the custom template this has to be resolved with a firmware update.

 

[OlegR_3CX]

@

Hope that helps you for correcting/adjusting the template going forward.

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.