V20 Office Hours / Timezone not working correctly

Fitdesk

Premier Customer
Joined
Oct 26, 2023
Messages
3
Reaction score
2
Hi All,

We have two departments:
DEFAULT
WA Users

DEFAULT
is set to Global Time Zone (AEST). Office hours: Mon-Fri. 8:30-17:00
WA Users is set to +8:00 Australia (Perth).

It was my understanding that if the WA Users department has a timezone set to "+8:00 Australia (Perth)", that the time should be regular hours compared to DEFAULT (8:30-17:00), however, the behaviour I found whilst testing is that users in the WA Users department were recieving an "office closed" voice prompt past 17:00 AEST. Which if their timezone is linked to the office hours, should not happen.

However, if I manually included the shift in time in the office hours in the WA Users department to 10:30-19:00 it began working operating correctly. Does this mean that the office hours is actually linked to the server timezone?? How would that account for daylight savings in that instance?

I double checked the user I was calling to test and they are definitely in the correct WA Users department (as their main dept) and also their Schedule is set to use default office hours (which I would assume is refering to their main department).
1749002961687.png


This has left me very confused as I would expect the timezones to be linked to the office hours, so if I were to set the timezone, then the office hours would be related to the timezone I set. But based on my testing this doesn't appear to be the case.
 
I just found this out:

Office hours for departments are still evaluated in the system (server) time zone, not the department’s local time zone — even if you configure the department's time zone.

This means:
  • The timezone field on a department is mainly cosmetic or organizational — e.g., for reporting, UI formatting, and possibly provisioning templates — not used for evaluating office hour logic.
  • So when a department sets its hours as "08:30–17:00", those hours are interpreted in the system (global) time zone, not the department's defined time zone.

    Is this correct? If this is the case, wouldn't organizations with multiple timezones have manually adjust the system when it switches? Or do they just use more than one instance of 3CX?


 
This should not be the case. You can set different timezone per department as this is also clarified in the guideline here.
But you also need to ensure that you have assigned the extensions to this specific department. You can confirm this from the General tab of the extension configuration:
1749006661832.png
 

Latest Posts

Forum statistics

Threads
111,945
Messages
589,867
Members
164,835
Latest member
Firefox Technologies