Date & Time Conditions stuck in GMT Timestamp?

AIC2000

Member
Feb 15, 2018
157
2
18
31
Anyone else noticed this? If the server is set in BST (British Summer Time), then time conditions are an hour out - even though being set by the FusionPBX popup calendar as the correct time. In dial plan, they are the correct time and date, but when the server is in BST - they don't kick in until an hour later.

Shame FusionPBX team took the issues tab off GitHub eh...
 
Last edited:

DigitalDaz

Administrator
Staff member
Sep 29, 2016
2,478
415
83
@AIC2000 The servers time should be set to UTC then adjust in the domains accordingly. Also, not a shame, worse IMHO, it damages the projects credibility both in terms of functionality but for many, transparency.
 
  • Like
Reactions: AIC2000

s1766333

New Member
Dec 2, 2017
13
3
3
"even though being set by the FusionPBX popup calendar as the correct time"
There isn't a popup calendar that changes time zone or server time.

You set the time zone in then FusionPBX Menu -> Default Settings -> Domain -> time_zone then select the right name.
 

AIC2000

Member
Feb 15, 2018
157
2
18
31
I said correct time, not timezone - I mean the little JS popup you get allowing you to select the time in the Time Conditions section of FusionPBX :)

It's OK though, I can resolve this by following @DigitalDaz recommendations. :D
 

brb5548

Member
Sep 26, 2018
53
7
8
42
I am noticing in 4.4 the 'time of day' check works great but the 'date & time' check isn't adhering to the time_zone variable for the domain even when the server is in UTC. The freeswitch confluence site appears to say that either time_zone or tod_tz_offset can be used for either of these dial plan conditions (minute-of-day or date-time). I don't think the fix would be at the FusionPBX layer but in the dial as it appears to support the offset and time zone corrections.
ref: https://freeswitch.org/jira/browse/FS-4741

I am still working through how to best address this but thought I would post my findings.
 

Craig Fox

New Member
Mar 21, 2018
18
1
3
50
Any update on this? I have also found that 4.4 does not pay attention to the timezone when calculating the offset. My fix has been to set the Day & Time schedule to UTC but this is not very intuitive.