Solved Global timezone not updating

[sam.phillips]

Kia ora guys,
I feel like I must be doing something wrong here...Server is up to date v16, Linux on AWS Lightsail. All I need to do is update the server timezone - it was original +12 Auckland, NZ, needs to be -6 Central Standard.

So in Settings > Timezone & Office Hours > Timezone is set to "-6:00 United States - Central Time"

However, when looking at call history, activity log or reports, the time reflected is still in NZ time.

Have tried service restarts, and a server reboot - no difference. Where is this going wrong?

Oh and server time (as in checked on the Debian CLI) reports the correct CST time.

 

[cobaltit]

I'm pretty sure it's not going to retroactively change time but only use the new TZ going forward.

 

[sam.phillips]

So we have made the timezone change, restart services (and even a server reboot). And then made new calls, and the new calls are still not showing the correct time.

 

[cobaltit]

Oh ok. It wasn't clear in your original post. I honestly don't know that I've ever tried to change the system time after an install. When you say the time is showing correctly in the CLI, do you mean the terminal via the management console or at the actual linux console or SSH?

 

[sam.phillips]

That's exactly my issue too - we've never actually needed to change the timezone haha!

Yep so both the 3CX "Terminal" and the actual server CLI report the correct time on the 'date' command.

 

[cobaltit]

Hmm. I dunno that I'm bored enough to try it myself. Maybe the next time I move our internal instance (which I do a lot).

Only thing I can suggest is maybe take a backup and then blow away the install and restore it, choosing the new TZ during the restore.

 

[sam.phillips]

Yea very tempting to be honest, wasted too much time on this already!! Will flick a proper support ticket through to 3CX.

 

[cobaltit]

Oh wait. Did you check to see if at the extension level it's set to use the global time zone vs an extension specific one? That might account for the discrepancy.

 

[sam.phillips]

Like on the phone provisioning for the extension? Yep, that's set to global.

However, the basic test I've been doing is just making an inbound call, and looking at the call history entry.

 

[cobaltit]

On the phone, in the 3CX app or in the management console?

 

[sam.phillips]

The 'Call History' from the management console (just via the Dashboard link).

Test call is just hitting an IVR.

 

[cobaltit]

I guess the only other thing to check is clearing your browser cache? Otherwise definitely interested in what support says.

 

[JohnS_3CX]

Hi,

The management console will adapt to the timezone of the computer accessing it.

So if you are seeing the "wrong" time it is most likely due to the now obvious reason, of using the same PC as before

Change your PC timezone and log back into the management console to see what a person of that timezone would see

 

[sam.phillips]

Haha yea I feel very silly now... Received this repsonse back from 3CX Support....

1. The time shown in the call history is taken from the local machine you are using to browse the Management Console.
2. If you log in to the Management Console from a different time zone then you will see the timezone of the local machine you are using.

 

[JohnS_3CX]

No worries Sam, glad to hear it was all cleared up

To be fair this is not a an often discussed feature, you mostly come across if you manage multiple PBXs in various time zones and have to change your PC time zone on a regular basis