Daylight Savings Time - Incorrect Start Date

[Callinectes]

A customer contacted us to let us know their phones are all showing the time as 1 hour ahead as of today. In one of the phone GUIs it shows DST starting today, 3/8, instead of the correct date of 3/13 for 2022. Please help.

 

[Callinectes]

FYI - March 8 was DST start in 2020

 

[SteveITS]

Time is correct on our server. I assume from your question the time zone and year are correct on your client's.

Is this a Linux/Debian server? The next thing that comes to mind is whether the OS updates have been installed? 3CX does this for Debian if automatic updates are enabled, otherwise they recommend against installing updates manually.

 

[Callinectes]

Time is correct on our server. I assume from your question the time zone and year are correct on your client's.

Is this a Linux/Debian server? The next thing that comes to mind is whether the OS updates have been installed? 3CX does this for Debian if automatic updates are enabled, otherwise they recommend against installing updates manually.

Yes, everything is set as it should be though I don't know how you can select a different year than the current year.

It is a Debian system. We do not touch the OS - everything done is handled via 3CX. It simply appears to be that it's using older DST dates/DST settings that aren't current for the phone provisioning. It can provision individual phones to different time zones but the dates stay the same though the time changes. For now I have had to set all phones to a zone 1 hour ahead and will revert at actual DST change but hoping there is a fix to prevent future issues.

 

[JohnS_3CX]

@Callinectes could you please provide all the info in one place so we can take a look at the issue?

• 3CX Version?
• OS Version?
• What you selected in 3CX > Settings > Timezone
• What phone models?
• What firmware they currently have?
• What setting they have in their extension timezone?
• Are you using custom templates?

 

[Callinectes]

@Callinectes could you please provide all the info in one place so we can take a look at the issue?

• 3CX Version?
• OS Version?
• What you selected in 3CX > Settings > Timezone
• What phone models?
• What firmware they currently have?
• What setting they have in their extension timezone?
• Are you using custom templates?

Sorry I didn't clarify that information,

• 3CX Version? - V18u3 (build 450) - Debian install from ISO in link available in portal
• OS Version? - Whatever is installed and updated via ^ and 3CX updates - we don't touch the OS
• What you selected in 3CX > Settings > Timezone? -7:00 US Mountain Time
• What phone models? Affects Poly SPIP335 and VVX500. Does not affect Yealink T46S or Poly VVX501.
• What firmware they currently have? Affected 335 4.0.10.0689, affected VVX500 5.6.0.17325
• What setting they have in their extension timezone? Default/Global
• Are you using custom templates? No

Note that the unaffected VVX501 shows DST setting of "Fixed Day" set to disabled and the Start Date set to second Sunday in March at 0200, where the affected phones show DST setting of "Fixed Day" set to enabled and Start Date set to 8 March at 0200. Since the templates have a variable in the parameter that affects the generated configuration file I would think it would be a simple update of the DST start date or to change to the same disabled Fixed Day setting as is applied to the VVX501. I realize these phones are unsupported and we are working on having the customer change them out - in fact the 335s are in the process of being replaced but the VVX500s may still be around for a while longer.

To deal with the problem we have set all of the affected phones to -8:00 Pacific Time which we will have to change back to -7:00 Mountain Time just prior to 13 March.

 

[JohnS_3CX]

Please be advised that there is a DST limitation when it comes to both those EOL models:
https://www.3cx.com/sip-phones/polycom-soundpoint-450-550-560-650-670/#h.inmoib1u9t0w
https://www.3cx.com/sip-phones/polycom-vvx-eol/#h.6chpwcv5ucba


This means there will not be any updates or support to change their behavior.

 

[Callinectes]

Please be advised that there is a DST limitation when it comes to both those EOL models:
https://www.3cx.com/sip-phones/polycom-soundpoint-450-550-560-650-670/#h.inmoib1u9t0w
https://www.3cx.com/sip-phones/polycom-vvx-eol/#h.6chpwcv5ucba


This means there will not be any updates or support to change their behavior.

Understood. FYI, however, I simply pasted the SNTP settings from the supported polycomvvxgen2 template into the EOL polycomvvx template via a custom template then applied that template to one of the phones, let it reprovision, and now the time is correct.