call report's time is not correct

Status
Not open for further replies.

Marco2018

Joined
Feb 9, 2018
Messages
3
Reaction score
0
hello, I want to get a report of yesterday, for example

from 2/7 12:00 am to 2/7 11:59 pm, but the first record is 2/7 8:08 am (please see figure 1)
and the last is 2/8 7:59 am (please see figure 2)

the time zone is utc-8 and the windows server time is correct
and the 3cx is up to date, 15.5.8801.3, windows version.

what can I do in this case? thank you!

--figure 1--
https://drive.google.com/file/d/1YEGes8C3PW2wlCafEfbY6FF4xTDWnFTt/view?usp=sharing

--figure 2--
https://drive.google.com/file/d/1BkdF-WRwZiU5_qiVlAcnt8KCGT0-alk3/view?usp=sharing
 
The 3CX server is a UTC-8 Timezone. Could you please check the PC you accessed the Management Console from as well though?
 
Bunner, I thought this was resolved yesterday and that's why I upgraded.
My box is correctly set and the settings in 3CX shows Pacific.
Today shows yesterday and yesterday shows day before.

Hopefully this will be resolved in SP4. Who needs reports anyway?

Can an SP3 backup restore to SP2?

Where do I get a linux SP2?
 
Last edited:
Can an SP3 backup restore to SP2?
No

Where do I get a linux SP2?
To view the available versions of a package: apt-cache policy 3cxpbx
Then to install the desired version: apt-get install 3cxpbx=<version number>
e.g. apt-get install 3cxpbx=15.5.6354.2
...but if you don't mind me asking, why?

@Marco2018
Still waiting for your update...
 
The reports are not showing the correct date as mentioned above by Marco
I posted that my timezone is correct on both the linux box and the 3CX console.

I'm on the Left Coast.
 
Call reports are still correct, just the call log is screwed up like in SP2.

Any answers from 3CX?
 
hello, I want to get a report of yesterday, for example

from 2/7 12:00 am to 2/7 11:59 pm, but the first record is 2/7 8:08 am (please see figure 1)
and the last is 2/8 7:59 am (please see figure 2)

the time zone is utc-8 and the windows server time is correct
and the 3cx is up to date, 15.5.8801.3, windows version.

what can I do in this case? thank you!

--figure 1--
https://drive.google.com/file/d/1YEGes8C3PW2wlCafEfbY6FF4xTDWnFTt/view?usp=sharing

--figure 2--
https://drive.google.com/file/d/1BkdF-WRwZiU5_qiVlAcnt8KCGT0-alk3/view?usp=sharing


Did your system auto update last night? Our call reports are NOT working correctly either. The automated reports are pulling yesterday's call log. I see nothing in the call log since the update. Our phones are working (16 of them) and our call recordings are working as well.
 
Same, "Call log" issues on all my servers after update. "Today" it show all calls from yesterday. No matter what, you can't see call log from today. Recordings and Reports are fine
 
No reply from 3CX last night regarding this and today. Silence.
Hopefully making a quick patch to put out this weekend.
 
At 1600 today all call logs showed up. 1600 in California is 0000, so while the clock is right, the date is one day off. Please fix this as looking at the call logs long after the day is done is pretty worthless.
 
The 3CX server is a UTC-8 Timezone. Could you please check the PC you accessed the Management Console from as well though?

Hi Nick,
We always set the time zone to be Pacific Time.
https://drive.google.com/file/d/1hd0w_YiDlTv4Am20oBqJa15nAY9H_Sii/view?usp=sharing
when I upload pictures, the forum say there was a problem to upload your file :).

I find the reports are correct till 2/1, and at that time we migrated the virtual machine to another host, which server's time may be not correct then, but fixed soon.

I think there may be a glitch in the report feature
since the report say the time range is
from 2/7 12:00 am to 2/7 11:59 pm, but the first record is 2/7 8:08 am (please see figure 1)
and the last is 2/8 7:59 am (please see figure 2)

FYI, I also try to search call log and that file on disk
I think my call log is good, I can find that record of similar time.
https://drive.google.com/file/d/1DBLBAGQnk1HjPpSxlYjPSPWJIm7aQ02_/view?usp=sharing

and this maybe that file
https://drive.google.com/file/d/15LFvN54z-RZIPBkcUniPsi8Aevb0OvKi/view?usp=sharing

I see the system is up to date, and the auto update is unchecked..
https://drive.google.com/file/d/1PcQAjdsZKRqaloYFtCETE8fJXYSdWySr/view?usp=sharing
 
Last edited:
I find the reports are correct till 2/1, and at that time we migrated the virtual machine to another host, which server's time may be not correct then, but fixed soon.
This may the problem because the math doesn't add up. Changing the Windows timezone does not necessarily mean that 3CX realizes it immediately, you must for sure restart the services, all of the them.

Please do the following to make sure:
  1. Check the Windows time, timezone and date to make sure it is correct now.
  2. Reboot the whole server. Not only the 3CX services. Start Menu --> Reboot
  3. Once everything comes back up, wait 2 days.
  4. After 48 hours have passed, pull a report with custom date/time for the previous day.

Forget about the reports that have been written so far, because if the data has be written to the DB, it has been statically incorrectly written and there is no way of fixing it.
Recheck the data for dates after restarting the PBX server.

I have been trying to replicate this but have not managed to do so so far.
 
We have the same problem on 2 machines on the West Coast. As I said before at 1600 the current logs propagate for the day but during the day we have nothing but last yesterday's logs.

I have reboot both servers and waited 48 hours and the same thing.

Please fix this ASAP
 
Same issue here - call log thinks today is yesterday. An automatic update happened on the weekend so I'm sure this is the issue. Runnig version 15.5.8801.3
 
Let's keep this at the top until resolved. This is a huge issue affecting many users.
 
This may the problem because the math doesn't add up. Changing the Windows timezone does not necessarily mean that 3CX realizes it immediately, you must for sure restart the services, all of the them.

Please do the following to make sure:
  1. Check the Windows time, timezone and date to make sure it is correct now.
  2. Reboot the whole server. Not only the 3CX services. Start Menu --> Reboot
  3. Once everything comes back up, wait 2 days.
  4. After 48 hours have passed, pull a report with custom date/time for the previous day.

Forget about the reports that have been written so far, because if the data has be written to the DB, it has been statically incorrectly written and there is no way of fixing it.
Recheck the data for dates after restarting the PBX server.

I have been trying to replicate this but have not managed to do so so far.
Thanks, Nick
After reboot and 48 hours, the reports looks good now.
 
As I've posted many times, after 4PM on the west coast we see all the logs for that day. Up until 4PM we see yesterday's logs. No reboot will fix that. Only a patch will fix that.
 
We have similar issue after update to SP3
Logs and call logs are find, but when we generate Report "Call report" it doesn't take account of timezone. To see a call that we made at 4:12 PM, we have to generate a report looking for calls between 13 and 14. Our timezone is UTC - 3
 
@jimbo59
@Greg S
@cjkoll
I believe you are referring to the Call Logs. The OP in this thread was referring to an issue with the Call Reports - 2 different things.
If this is the case, please update the relevant thread.

@Marco2018
Glad to hear it is good now. :)

@jhonku
2 questions as this can sometimes be confusing with timezones.
The actual server where 3CX is installed on, what timezone is the OS set to use? Also is it Linux or Windows? (if it's Linux you will have to SSH on to it to see this)
Then, the PC from which you logged into the Management Console to create the Report, what timezone was that PC set to?
 
Nick, I send you an example

Server Timezone y Time

C:\Users\AG-SERVER>tzutil /g
Montevideo Standard Time
C:\Users\AG-SERVER>time
La hora actual es: 10:42:21,65

PC Timezone y Time

C:\Users\simpletech>tzutil /g
Montevideo Standard Time
C:\Users\simpletech>time
The current time is: 10:43:12,64


Test Call
02/13/2018 10:21:40 PM Prueba Seba (0000) 099087980 00:00:05

Reports

Empty report.PNG Reports Time differences.PNG
 
Status
Not open for further replies.