Timezone setting at DID level?

[Csut12]

Can 3cx add Timezone setting at the DID level?

Why: Multiple phones/DIDs in different time zones. After hours routing triggers 3 hours early on a DID for east coast when server is west coast.

It seems there are couple area within 3cx for hours/timezones settings:

• Timezone at System level: example - PST
• [irrelevant] Timezone at hardware phone display
• Office Hours at System Level: example - 8AM-5PM
• Office Hours at Trunk level (optional – not yet used)
• Office Hours at DID rule level (optional – not yet used)

Setting office hours at the Trunk or DID level has following drawbacks:

1. Doesn't support Daylight savings adjustments based on location
2. Duplicating office hours across multiple DIDs means bigger chance of typo/error.
3. We are not trying to get custom office hours, but same hours at each location.

It seems like a Timezone setting would be useful for the DID and Trunk level.

 

[BLS_LeeR]

Did you find a solution?

 

[MarkNAS]

Did you find a solution?

The unreleased V18 Update 6 is bringing timezones and custom holiday ranges to the extension group level. So you should be able to route the DID to an extension group and the local Timezone should take over. Not quite what is being asked for but will probably be the recommended solution besides

 

[Csut12]

Yes V18 Update 6 adds timezone support at the extension group level and that seems like it could work.

For now actually scrapped office hours (by setting same queue for office hours and after hours) in favor of identical behavior 24/7 - we may adopt the group level timezone support at some point though if needed.

 

[Paul Bottrell]

I'm not finding the Timezone options for Extension Groups in V18 Update 6.
Maybe looking in wrong place.

 

[MarkNAS]

I'm not finding the Timezone options for Extension Groups in V18 Update 6.
Maybe looking in wrong place.

Are you looking in the webclient > admin section? It’s not visible in the management console under extension groups.