Extension Custom Hours didn't function properly for Daylight Savings

[JimD]

Good morning,

In the USA, we experienced daylight savings time yesterday. This morning, my 3CX system did not properly adjust and our business didn't get calls for an extra hour. The time on the Windows server 3CX is installed on, is correct. Hours must be wrong somewhere in the system as our extensions didn't open for an extra hour today, so people sat there with no calls.

For the setup of this queue we had trouble with - I use an extension with specific business hours. When a person calls into our main DID/digital receptionist, if they select option 3- they go to extension 1112-Main Queue Transfer. Depending on the hours, the extension either sends them into a queue or tells them we are closed. It didn't route people into the queue for an extra hour today.

Thanks,
Jim

 

[leejor]

I assume you've gone through all of this?

https://www.3cx.com/blog/docs/setting-windows-server-time/

If you get a Voicemail, is the receive time given, correct?

See the last post in this tread...
https://www.3cx.com/community/threa...ault-time-zone-of-3cx-phone-system-v15.46615/

 

[Spyderbane]

I have the same issues. I ended up setting the time zone from Pacific to Mountain. Which bugs me as I rather see a zone that says Pacific DST.

 

[JimD]

I assume you've gone through all of this?

https://www.3cx.com/blog/docs/setting-windows-server-time/

If you get a Voicemail, is the receive time given, correct?

See the last post in this tread...
https://www.3cx.com/community/threa...ault-time-zone-of-3cx-phone-system-v15.46615/

Voicemails seem to have the correct timestamp. Using the post in that referenced thread - I am set at "-5:00 United States - Eastern Time", which seems correct.

 

[JimD]

I have the same issues. I ended up setting the time zone from Pacific to Mountain. Which bugs me as I rather see a zone that says Pacific DST.

You have the same issue - today? Odd the fix would be to use the wrong timezone. I've been using 3CX for years and have never had to think about DST.

 

[JimD]

From what I just read - system time like logs would use the Windows server time ,where as office hours would use that timezone setting in Settings->Timezone, Office Hours, Holiday.

So does that mean the fix is to actually change my time zone from -5 Eastern Standard to -4 Chili, or any other -4 timezone?

That seems ridiculous.

 

[JimD]

I guess I'll move to a -4 timezone during DST - which really makes no sense on a system like this.

 

[JCarnes]

Same thing happened with our systems. We are using dummy extensions to route calls based on time. Windows system time/timezone is correct, and the Timezone for 3CX is correct. However, the extensions did not start processing calls until an hour later. Running 3CX v15.5.15502.6.

Is the correct action at the moment to use the wrong Timezone in 3CX, Windows, both?

 

[JimD]

Not sure, that's what I'm trying. I just adjusted to a -4 timezone and my queue that's scheduled to close at 7 is still open which is correct, and the one that closed half an hour ago is closed... So that's correct.

I have a ticket in with support but don't have any good information to share yet.

 

[cobaltit]

@YiannisH_3CX @JohnS_3CX

Can either of you shed some light on this?

 

[JimD]

@YiannisH_3CX @JohnS_3CX

Can either of you shed some light on this?

I can confirm office hours, including extension specific ones, worked as they should when I manually changed my time zone from Eastern Standard to one an hour different. Other functions that use server time we're fine throughout this.

 

[JohnS_3CX]

As per the ticket opened, the issue is under investigation by our support department and you will receive an update from there.