Daylight Saving Time - Office hours

[Samfiller]

Is there some where that states the time that 3cx thinks it is?

Early this morning we switched to daylight saving time, The server is windows set to auto up via NTP and shows the correct time.
3cx in TimeZone shows Eastern-
It appears all our office hour rules in 3cx did not update causing the office hours to be off by an hour-

Any thoughts on this?

Is there a script that 3cx runs to manage the auto switch that may have run prior to the "switch that would cause this" ?

 

[nub]

it could be the phones not 3cx

 

[Samfiller]

The phones are fine- its the "office hours" auto switch that is the issue.

 

[Yellow_Flash]

I've faced the issue myself.

I manually change the Office times and save it.
Instead of 9 am, i change it to 8 am. It does the trick and the system goes online at 8.
Once it is online, I go back and edit the office time back to original one and the system goes offline and comes online at 9. Takes hardly a min to do this.

Or you can restart the services.

Both of them have worked for me.

 

[VasilisV_3CX]

Hi @Samfiller,

Could you describe which feature was not being updated? Was it an inbound rule or extension statuses not changing accordingly to the DST?

 

[Yellow_Flash]

I

Hi @Samfiller,

Could you describe which feature was not being updated? Was it an inbound rule or extension statuses not changing accordingly to the DST?

I believe he is talking about the Auto-Switch.
The one where extensions automatically switch from DND to Available during office hours.

 

[Alphabetic]

Depending on your install:-

Windows - from the desktop time
Debian ISO self hosted - Terminal > Date command
3CX Hosted - Can see the locale from instance manager, to check the time you'd need to contact support.

 

[SteveBohn]

Had the same issue this morning on at least two different systems (may have been more but we only heard from two clients). Both systems checked out to be perfectly fine (on-prem servers, Patton devices, phones, etc., all showed the correct date/time). Both of these clients have a "call flow control" extension that handle their office hours (auto-switching). I had to set both manually to "in office hours".

 

[JohnS_3CX]

Is there some where that states the time that 3cx thinks it is?

Early this morning we switched to daylight saving time, The server is windows set to auto up via NTP and shows the correct time.
3cx in TimeZone shows Eastern-
It appears all our office hour rules in 3cx did not update causing the office hours to be off by an hour-

Any thoughts on this?

Is there a script that 3cx runs to manage the auto switch that may have run prior to the "switch that would cause this" ?

Clock must be able to sync to NTP, then the rest is handled like so:


- Windows: Correct timezone selected in management console & MUST be selected in Windows Regional settings too

- Debian: Correct timezone selected in management console

 

[David Liddle]

We observed this same behavior with our installation this morning. The server (3CX Pro 16.0.9 on Debian 9.13) and the phones (1x Snom D375, 2x Snom 320, firmware current) displayed the correct times, but the automatic status changes were delayed by one hour.

 

[manfer]

Looks like
https://www.3cx.com/community/threa...g-correctly-after-daylight-saving-time.71434/
has never been addressed

 

[David Liddle]

We observed this same behavior with our installation this morning. The server (3CX Pro 16.0.9 on Debian 9.13) and the phones (1x Snom D375, 2x Snom 320, firmware current) displayed the correct times, but the automatic status changes were delayed by one hour.

Now I see in the log for my own phone that it received correct information about DST in its periodic time check:

Mar 28 01:49:53.001 [NOTICE] PHN: DST start 28.03.2021 02:00:00 end 31.10.2021 03:00:00 offset 3600

However, one doesn't see the clock advance in the log until 03:00:

Mar 28 02:59:35.828 [NOTICE] SIP: process auth: Match challenge for user ********
Mar 28 04:00:35.870 [NOTICE] SIP: process auth: Match challenge for user ********

Is there perhaps a connection?

 

[NickD_3CX]

Hi!

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 aspects of 3CX that sometimes didn't trigger.

Hopefully this will be the last time you will have this as V18 is due out within the next few weeks.