Hello Good people,I am facing issue with one of my domain in fusion with time condition.I havee created a time condition which was working fine .but suddenly i see a time issue.like i am setting a condition to be true on this (9am-10pm) but when my local time is get 7pm that (9am-10pm) condition get false and it start to play the my after hours message.What i observe that fusion pbx probably running 3 hours of ahead of my time.In my default setting I can see its set the correct time zone that i am (gmt+6) .Any one have any clue why this happening? see the attached picture
Time condition not working properly
- Thread starter roney_ewu
- Start date
- Status
Hey guys, sorry to bring this up, but I'm seeing same issue on F4.4.11
date on system is right cdr and others ok too, but time condition on one domain specifically is applying out of time by 1h.
This domain has not a different timezone from default, amd postgresql using localtime, same as system.
Even enabling debug log I see both Date/Time condition matches (PASS on dialplan), but can't see what time is based to process that.
RFC Date shows correctly for the call too.
Any advice on how can I troubleshoot this?
Thanks!
date on system is right cdr and others ok too, but time condition on one domain specifically is applying out of time by 1h.
This domain has not a different timezone from default, amd postgresql using localtime, same as system.
Even enabling debug log I see both Date/Time condition matches (PASS on dialplan), but can't see what time is based to process that.
RFC Date shows correctly for the call too.
Any advice on how can I troubleshoot this?
Thanks!
One thing to be aware of, is that the logic can sometimes catch you out depending what units you choose. For example, if you use "Hour of day" and choose the range 09 to 17, this actually gives you 09:00 to 17:59. I have seen many people get caught with that one and it appears as if the condition is an hour out at the end of the day.
Hi Adrian, thx for reply, and sorry not to update.
Yes I know about that, but was not that, but already solved.
My issue was about the timezones definition file from FS is not updated properly.
grep Buenos /etc/freeswitch/autoload_configs/timezones.conf.xml
<zone name="America/Argentina/Buenos_Aires" value="ART3ARST,M10.1.0/0,M3.3.0/0" />
Should be just ART3. I think the other part is setting a DST while there is no more since years really.
Yes I know about that, but was not that, but already solved.
My issue was about the timezones definition file from FS is not updated properly.
grep Buenos /etc/freeswitch/autoload_configs/timezones.conf.xml
<zone name="America/Argentina/Buenos_Aires" value="ART3ARST,M10.1.0/0,M3.3.0/0" />
Should be just ART3. I think the other part is setting a DST while there is no more since years really.
- Status