XAPI Call Log Data Report - CallId value is always '1'

[voipmaster32]

After we updated our phone system to V20 around 14/08/25, any reports retrieved via the xapi/v1/ReportCallLogData route results in a CallId value of '1'. Even if multiple call logs are returned in a single response, they all have 1.

Example snippet of API response (data has been sanitised, but CallId is "1" for every record in actual response):

{
"@odata.context": "https://[HOST]/xapi/v1/$metadata#ReportCallLogData",
"value": [
{
"MainCallHistoryId": "00000000-123...",
"CallHistoryId": "00000000-456...",
"CdrId": "00000000-789...",
"CallId": 1,
"Indent": 1,
"StartTime": "2025-12-01T05:26:15.441391Z",
...
},
{
"MainCallHistoryId": "00000000-321...",
"CallHistoryId": "00000000-654...",
"CdrId": "00000000-987...",
"CallId": 1,
"Indent": 1,
"StartTime": "2025-12-01T05:27:15.441391Z",
...
}
]
}

Anyone else come across this or have any information that might help make sense of this?

 

[KyriacosS_3CX]

Hello,

Since update 6 the database structure for storing calls was changed, and calls have a different ID structure.

You can begin reading about it here: https://www.3cx.com/blog/releases/v20-u6-cdr-output/

 

[voipmaster32]

Hello,

Since update 6 the database structure for storing calls was changed, and calls have a different ID structure.

You can begin reading about it here: https://www.3cx.com/blog/releases/v20-u6-cdr-output/

Thanks but could you explain what the CallId field is specifically and why it's '1'? That seems a bit redundant