Extension custom hours don't function properly for daylight savings

Status
Not open for further replies.

HExSM

Forum User
Joined
Feb 18, 2019
Messages
85
Reaction score
11
Yesterday the time was changed to daylight saving time. Our custom business hours are all 1 hour off now. The server time is correct.
Do I really have to set the time zone manually twice a year? This should work automatically.
 
Hi @HExSM,

You should not need to set the time manually, provided the timezone you're using is utilizing DST. How are you hosting this instance? What OS is it running on? How did you check the time on the system?
 
We have the exact same issues with 3CX for years now. There is a bug in the software causing time errors when it's daylight saving time and a time shedule is set on an extension.
 
Hi @HExSM,

You should not need to set the time manually, provided the timezone you're using is utilizing DST. How are you hosting this instance? What OS is it running on? How did you check the time on the system?
The instance is running on a vServer, running Debian 9.
I checked the timezone with date +%Z which returned CEST.
 
Hi!

I mentioned this in another thread today, I have had a word with your dev team and we have included some changes in V18 that should solve the DST issues for all components of 3CX that sometimes didn't trigger.

This should be the last time you see this as V18 is due out within the next few weeks.
 
  • Like
Reactions: HExSM
Status
Not open for further replies.