Date and time issue, office hours setting

[FACCR]

My 3cx was working perfectly, set to accept calls from 8am and reject at 6pm. About 3 days ago, he started rejecting calls within the allowed time. I noticed that the calls were being forwarded as if it was outside business hours.

I checked the team zome and it's correct. The logging time is according to the timezone I am from (Brazil UTC -3). Despite showing the correct time in the logs, calls are not accepted, appearing to have the wrong time.

In settings, parameters, TIME_NTP_SERVER was with the server pool.ntp.org and I changed pool.ntp.br, but it was no use.

In settings, Timezone & Office Hours Settings, I'm using -3 Brazil (on DST).

Can anyone help me fix this problem with the time? Is there any place inside the 3cx system that I can check the current time?

Regards.

 

[FACCR]

Maybe I've found a bug.

If I use timezone -3 Brazil (DST), the time does not match with the current time.
If I use timezone -3 Brazil (in DST), the time does not match with the current time.
However, if I use timezone -3 Argentina (Buenos Aires), the time matches with the current time and everything works.

Version Number

16.0.461

 

[AWS2P]

May be you're right, need to be seen by 3CX Staff to confirm @YiannisH_3CX or @NickD_3CX

try to push an update to latest beta SP4

 

[FACCR]

@aws2p Thanks for your reply. About the beta update, I'm not comfortable using a beta version in production.

 

[AWS2P]

you already use if your version number is right, can you check?

 

[FACCR]

16.0.4.461 - this is my version number. Am I using a beta version?

 

[AWS2P]

Yes, as latest production release is 16.0.3.676 for now

 

[AWS2P]

So you can try to push the latest beta 16.0.4.485 and see if problem is fixed

 

[JohnS_3CX]

Hi,

We are aware of the issue and will be addressed in a future upgrade.

For the time being if the Argentina time zone works well for you, it should be ok to keep it there.

 

[FACCR]

Thanks for the help @JohnS_3CX and @aws2p

 

[AWS2P]

you're welcome