Do anyone else's Yealink phones have messed up daylight savings time (UK) today?

[OlegR_3CX]

@

I'm in france. as the timezone has made the time change early. Is the time wrong only on the phones or also on the server? If yes for the server, does this affect the office hours for incoming calls in the current configuration.

Hi there. The issue has only to do with the endpoint and Yealink devices displaying the wrong time and not the Phonesystem itself and the routing of the calls.

 

[JulienI]

Hi,

same issue here in France, but looking at the T54W phone template from an up-to-date 3cx18 :

#Configure the daylight saving time feature; 0-Disabled, 1-Enabled, 2-Automatic (default);
local_time.summer_time = 2

#Configure the DST type when the DST feature is enabled; 0-By Date (default), 1-By Week;
local_time.dst_time_type = 0

#Configure the start time of DST. The default value is 1/1/0.
#If the DST type is configured as By Date, the value format is Month/Day/Hour. For example, the value 5/20/10 means the start time is at 10:00 on May 20. 
#If the DST type is configured as By Week, the value format is Month/Day of Week/Day of Week Last in Month/Hour of Day.
#For example, the value 1/4/2/5 means the start time is at 5 o'clock on Tuesday of the 4th week in January.
local_time.start_time = 3/28/2

#Configure the end time of DST. The default value is 12/31/23. The value format is the same to the start time.
local_time.end_time =  10/25/3

Do I correctly understand the settings as :

• if DST is automatic, then the other settings are no used, and DST switch is hardcoded into the firmware?
• whether the above is right or not, and as the template set the switch on a "per date" basis, the dates for DST switch are not right (28 march and 25 october)

So to fix, we have to :

• fix manually on the phone (but what happens when phone reprovision or reset)
• wait for a new firmware with "automatic switch" logic fixed
• update the template with the correct settings, which should be on a "by week" logic I think

Did I miss an option for the fix ?

Thanks,

 

[JulienI]

edit: below changes are working fine. Going to apply on self-hosted instances. Is there a way to apply these on instances hosted by 3CX on our own ?

Looking at https://support.yealink.com/en/portal/knowledge/show?id=64995b6e6a27da76bd0719b9&title=DST Configuration and how 3CX templates are generated :

#Configure the daylight saving time feature; 0-Disabled, 1-Enabled, 2-Automatic (default);
local_time.summer_time = 2

#Configure the DST type when the DST feature is enabled; 0-By Date (default), 1-By Week;
local_time.dst_time_type = 0

#Configure the start time of DST. The default value is 1/1/0.
#If the DST type is configured as By Date, the value format is Month/Day/Hour. For example, the value 5/20/10 means the start time is at 10:00 on May 20.
#If the DST type is configured as By Week, the value format is Month/Day of Week/Day of Week Last in Month/Hour of Day.
#For example, the value 1/4/2/5 means the start time is at 5 o'clock on Tuesday of the 4th week in January.
local_time.start_time = %%param::time_dst_start_month%%/%%param::time_dst_start_day%%/%%param::time_dst_start_hour%%

#Configure the end time of DST. The default value is 12/31/23. The value format is the same to the start time.
local_time.end_time =  %%param::time_dst_end_month%%/%%param::time_dst_end_day%%/%%param::time_dst_end_hour%%

could be changed to something like:

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%%

is this right ?

 

[JohnMorris]

Can 3CX not issue a new template for Yealink devices with the DST settings corrected?
If we edit the template this makes thes devices unsupported?