CUBE CDRs contain only large integers

[AdamB32212]

We are having a problem that I could not find any post/resource about (it's probably a rare occurrence, though it's consistent in our environment).

We configured generation of CDRs locally per the following (we are using ASR 1001-x):

gw-accounting file
primary ifs flash:cdrs_our-hostname.log
maximum buffer-size 40
maximum retry-count 3
maximum fileclose-timer 720
cdr-format compact

BTW, I also tried cdr-format detailed - no luck.

And when we make calls, all we get in the CDRs are long integers. Here's an example of the contents of a CDR file:

1690869958
1690873558
1690877158
1690880758
1690884358
1690887958
1690891558
1690895158
1690898758

It makes no sense. I know that in the past we were getting CDRs with comma-separated values reflecting calling and called numbers, time of the call, etc. But then from some point onward, all we get are those large integer numbers.

Has anyone seen anything similar? What could be the reason?

[b.winter]

Maybe it's the unix time format for a timestamp?
Without any further information, in which "column" this value is, it's just mind reading^^

[b.winter]

Your first value would be:

But AFAIK, this hasn't changed. So I don't know, why you think this is a problem or why are you so surprised?

[AdamB32212]

But this is all that is there. CDR should contain the values associated with the calls. 

Unless CUBE generates empty CDRs with just the timestamps when there are no calls?

[AdamB32212]

OK, I figured it out. When there are no calls through SBC, the CDR will contain timestamps without any call records per se. When calls are there, there is all the info that we expect. It's just odd that those timestamps are added when there are no calls.

Anyway, this issue is now resolved. Thank you!

[b.winter]

To me, it wasn't clear in your original post, that you only get those values in the CDRs and nothing else.