Carrier Log Inaccuracies

[elyc1990]

Hi all,

I tried calling myself to check the accuracy of carrier log (Admin Utilites > Carrier Log Report). I realize that it does not record time accurately.

Eg I pick up the call and answer for 10seconds but the "Dial Time" shows 7 seconds and "Answered Time" shows 0 second. If I didn't pick up the call, both "Dial Time" and "Answered Time" show 0 second.

Can anyone please help me debug this?

I'm running scratch install with the following version:
VERSION: 2.14-636a
BUILD: 171011-1450

[mflorell]

Those numbers come from the asterisk channel variables, and they are known not to be accurate. There isn't much you can do about it.

[blackbird2306]

Yes, you cannot rely 100% on these values, but for a better overview try this:
Report --> Admin Utilities --> Export Calls Report Carrier
1. Select "Export Fields" with "Extended" for detailed information.
2. Download and open the sheet with Excel.

Here are the values you are looking for:
Dial Time (only filled if there was an answer) = how long time it took until there was an answer
length_in_sec = connection time (billing time)

and for the 0 seconds Dial Time fields (no answer, busy and so on) you can use a trick:
Dial Time (convert in seconds look in excel forums for help) = (carrier log call_date field) - (dial log call_date field)

[elyc1990]

Thanks Matt and Blackbird!

Just a follow up Blackbird, the length_in_sec for manual calls include "Dial Time". Is this normal?

One more question, may I know what is the difference between Dial Log and Carrier Log in the "Export Calls Report Carrier"? Because the SIP Response in the columns "dial log sip_hangup_cause" and "carrier log sip_hangup_cause" can be different sometimes.

[blackbird2306]

As we have mentioned above - all these values are not 100 % . Sometimes it's possible that length_in_sec includes some extra seconds mixed with Dial Time but normally not.
Dial-Log hangup cause (db table vicidial_dial_log) and Carrier-Log hangup cause (db table carrier_log) values are generated from different database tables. But the codes from both are identical for me.