- Joined
- May 11, 2017
- Messages
- 31
- Reaction score
- 1
We have some customers who are really keen on using the new CDR's to build their own reporting tools in PowerBI.
So, to get ready for their questions, I've installed the new version 6 RC.
Managed to get the new CDR's to come in to PowerBI using a connection to PostgreSQL server.
Data is coming in ok.
But, I can't figure out how to get the time of the call from the new CDR's.
The blog post explaining the new CDR's says it's "A 16-character, zero-padded, hexadecimal representation of the UTC timestamp since the epoch".
So, if this is my cdr_id {00000000-01DB-C391-9E82-7F1A000001FF} I'm assuming the 00000000-01DB-C391 is the time?
If I convert 01DB-c391 to human-readable time it's 27th Dec 1970
I've checked the time on the server, and that is correct.
And, in the call log report, the same call shows with the correct time.
So, my question is: how do I convert 00000000-01DB-C391 to say 13th May 2025 11:00? (NZ Time)
Thanks,
marc
So, to get ready for their questions, I've installed the new version 6 RC.
Managed to get the new CDR's to come in to PowerBI using a connection to PostgreSQL server.
Data is coming in ok.
But, I can't figure out how to get the time of the call from the new CDR's.
The blog post explaining the new CDR's says it's "A 16-character, zero-padded, hexadecimal representation of the UTC timestamp since the epoch".
So, if this is my cdr_id {00000000-01DB-C391-9E82-7F1A000001FF} I'm assuming the 00000000-01DB-C391 is the time?
If I convert 01DB-c391 to human-readable time it's 27th Dec 1970
I've checked the time on the server, and that is correct.
And, in the call log report, the same call shows with the correct time.
So, my question is: how do I convert 00000000-01DB-C391 to say 13th May 2025 11:00? (NZ Time)
Thanks,
marc



