FreePBX CDR and CEL Analysis

[EddieJennings]

I'm tasked with providing a few folks a monthly report about call volume. This report is the result of me going through CDR records, doing a little math, and putting the results in a document. The CDR records for FreePBX look a bit different than what I had with Altigen; thus, I want to make sure I'm interpreting what I see correctly.

The CallerID (first redacted column) has the same value for both entries, as does DID (2nd redacted column) and the destination (3rd redacted column). The CallerID is an outside number. DID value must becoming from the inbound route as I have my DIDs configured there, rather than on the extension. The destination is the appropriate extension where said inbound route should send the call.

I'm curious why there are two CDR records, each with the same System value (blue number), but one with the disposition of no answer, and the other with answered? So, to dig further, I click the System value, which gives me the CEL.

Redaction

• CNAM: Red = Caller's CNAM; Black = Display Name for user's extension
• CNUM: Red = Caller's number; Black = User extension number
• ANI: Red = Caller's number; Black = User extension number
• Exten: Long red box = User's DID from the inbound route; Short red box = User's extension number
• Channel: Red = User's extension number

Here is what I think happened on this call.

1. Caller called the user as a potential party for a conference call.
2. My user answered.
3. Caller pressed their button to complete the conference call (which is why you see entries about a Bridge)
4. Call comes to a close, and my user hangs up, then the caller hangs up.

Ok, Eddie, I've looked at all of this. What's your question? FFS, man!

1. Am I right in the fact that this was likely a conference call initiated by the outside caller?
2. Am I right in believe the above keeps the original caveat I gave my user who requested this information true? The records I pull might include more events than "calls", such as conference call events; thus inflating the number of actual calls if I just give you the raw number of events.
3. Is there any kind of module that would give this user what they want (Number of inbound and outbound calls for X extension during Y period -- added bonus would be average call duration for Y period)?

Bear in mind this user is (unfortunately) fine with the lack of precision, as I've given them numbers from the CDR in the Altigen system. I figure since I have FreePBX, it would be a good time to revisit how I can gather some measure of precision.

[JaredBusch]

This is complex because the CDR shows EVERYTHING that happens.

Look at this example form when a sales guy called me.

They called in, hit my extension from the IVR. That is the .1002
I did not answer and so it rang out to my my Find Me Follow Me group.
The .1002 still ringing my ext and the .1010 ringing my mobile.
Then you can see I picked up on my Extension.

You are going to want to simplify this for a managerial call report.

[EddieJennings]

@jaredbusch said in FreePBX CDR and CEL Analysis:

This is complex because the CDR shows EVERYTHING that happens.

Look at this example form when a sales guy called me.

They called in, hit my extension from the IVR. That is the .1002
I did not answer and so it rang out to my my Find Me Follow Me group.
The .1002 still ringing my ext and the .1010 ringing my mobile.
Then you can see I picked up on my Extension.

You are going to want to simplify this for a managerial call report.

I agree about simplification. For the Altigen stuff, I made a little document that was a summary, and also provided the CDR in case they wanted to troll through the actual logs. There was a good bit of manual work that went into creating my summary, so I'm trying to think through how I can automate this. I thought about trying something like this.

1. Take the CSV I can generate from the CDR reports module.
2. Filter the records to show the destination as X, where X is the extension that I want to see the number and length of inbound calls.
3. Of these records, find the number of unique system IDs.
   However, that still not going to give a precise number of calls.

[JaredBusch]

@eddiejennings A unique ID is a call. How wold you think that it is not a valid representation of calls?

[JaredBusch]

@jaredbusch said in FreePBX CDR and CEL Analysis:

@eddiejennings A unique ID is a call. How wold you think that it is not a valid representation of calls?

Also, if you only care about calls to and from the outside world, run a CDR report from your SIP trunk provider.

[EddieJennings]

@jaredbusch said in FreePBX CDR and CEL Analysis:

@eddiejennings A unique ID is a call. How wold you think that it is not a valid representation of calls?

Yeah. . . I was having a dumb moment yesterday. I've actually taken a step back and asked the user to review with me what information they're actually wanting. I'm taking the angle of "now that we have FreePBX, let's see if [your information needs] can be better met."