"@odata.context": "https://domain.3cx.us/xapi/v1/$metadata#CallHistoryView",
"value": [
{
"SegmentId": 146,
"SegmentStartTime": "2024-02-08T11:00:13.301558Z",
"SegmentEndTime": "2024-02-08T11:00:13.473239Z",
"SegmentActionId": 6,
"SegmentType": 1,
So the XAPI log is not using the right timezone?I have -5:00 United States - Eastern Time selected, the call log does reflect the correct time based on that setting though.
I should have mentioned I'm actually using the API, not the CDR server so my bad on that...
Code:"@odata.context": "https://domain.3cx.us/xapi/v1/$metadata#CallHistoryView", "value": [ { "SegmentId": 146, "SegmentStartTime": "2024-02-08T11:00:13.301558Z", "SegmentEndTime": "2024-02-08T11:00:13.473239Z", "SegmentActionId": 6, "SegmentType": 1,
Precisely, in my case its off when comparing to the dashboard call log.So the XAPI log is not using the right timezone?
That's interesting. I'll check mine and see.
I did try another timezone, like -3, restarted all services and the api results remained unchanged, so seams to be completely ignoring that setting.Definitely sounds like a bug or something. Checked mine and the timezone in the log is UTC, 5h ahead of my EST time.
Can you switch your timezone to the EST Canada Montreal, just for fun? Also, what timezone is your computer using?

Being hosted by 3CX is apparently the issue.@Charles_3CX I confirmed that mine is fine, but I am self-hosted. Is the XAPI data influenced by the system timezone or anything like that?
Paul, make sure your departments are using the system timezone, and that they all correspond:
View attachment 40120


Correct, the same.What's your local PC timezone? Same I'm guessing?
That would be perfect, I appreciate it.I would open a ticket with 3CX. I can open that on your behalf if needed since we're linked.
DM me a support info package please.That would be perfect, I appreciate it.
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.