Discussions (English)

Registered 1 year 195 days

vt Thursday, 7 March 2024, 10:01 PM

reporting.events time jump

Dear Innovaphone Forum,

We are doing some analytics using the reporting schema, that contains two important tables for us: cdrs and events.

cdrs have a nice utc timestamp, but some detailed information is not available. To get that one has to join that information with the events table via the cdr_id.

events table unfortunately does not have a nice utc timestamp. It only has a seconds since system start value under 'time' column.

That means the values in this time column are continuously increasing and then suddenly drops to 0 on restart and start increasing again.

This makes it somewhat difficult to map that back to a usable timestamp, but not impossible

We've implemented a ~kompex system to manage all that and it's been working for more than a year.

This February we've got a situation when this value suddenly increased and continued from there.

This naturally caused a pretty big problem for us.

My questions:

- why did the time suddenly jump in a middle of a call? What can we do to prevent this?

- is it planned to add a proper utc timestamp to this table?

Thanks,

Viktor

innova_event_time_jump.JPG

Registered 7 years 341 days

Muschelpuster Thursday, 7 March 2024, 10:34 PM

Re: reporting.events time jump

Hello Victor,

I can’t answer this question, but are you sure that you need the events table? I created also some reports, but I do this with the cdrs table. The challenge is to interpret this table. You have mostly more then 1 row per call. So it‘s difficult to find the record with the result you want. Especially group calls deliver many rows with a lot of informations.
Which information you miss aim cdrs?
Just an idea: Maybe the events are created on different PBXs / gateways. Then there are logically different uptimes…

Niels

Registered 1 year 195 days

vt Friday, 8 March 2024, 11:03 AM

Re: reporting.events time jump

Hi Niels,

thank you for your answer.

cdr do not contain all detailed information, like which button was pressed, what type of busy signal was generated, redirects to waiting queues are also much nicer to analyze via events.

Yes, the multiple PBXs / gateways is a good idea, I'll check, what is suprising tough that we've never had this "switch" before...

You are here