- Joined
- Jul 2, 2017
- Messages
- 12
- Reaction score
- 0
Hi all,
I'm working for a company as a web developer and have taken on the task of installing and maintaining their 3CX instance. My boss has requested that the phone not ring outside of office hours, so I thought "Great, that's easy enough, I'll just configure an out of hours destination."
I awoke this morning to a message from the operations manager stating that no calls were coming through and that the phone was in out of hours mode and shouldn't be. Upon investigation, I found that it is likely to be a timezones issue.
We are based in the United Kingdom, which follows Daylight Savings (DST). The server is configured to use UTC. In 3CX timezone settings, 00:00 United Kingdom (London) is selected. However, the clock is still behind by an hour and voicemail timestamps are also behind by 1 hour.
However, elements such as the event logs are in UK time as expected.
Any solid solution to this that doesn't break when we go from BST (GMT+1) back into GMT would be appreciated.
Kind regards,
Edan Brooke
I'm working for a company as a web developer and have taken on the task of installing and maintaining their 3CX instance. My boss has requested that the phone not ring outside of office hours, so I thought "Great, that's easy enough, I'll just configure an out of hours destination."
I awoke this morning to a message from the operations manager stating that no calls were coming through and that the phone was in out of hours mode and shouldn't be. Upon investigation, I found that it is likely to be a timezones issue.
We are based in the United Kingdom, which follows Daylight Savings (DST). The server is configured to use UTC. In 3CX timezone settings, 00:00 United Kingdom (London) is selected. However, the clock is still behind by an hour and voicemail timestamps are also behind by 1 hour.
However, elements such as the event logs are in UK time as expected.
Any solid solution to this that doesn't break when we go from BST (GMT+1) back into GMT would be appreciated.
Kind regards,
Edan Brooke