Cisco CDR - extracting the call type: Incoming, Outgoing, etc

[shira.cohen1]

Hi All,

I am trying to analyze a call direction (Incoming,Outgoing, Internal, Trunk to Trunk) from a given CDR.

But I cannot understand which field (or fields) can supply the information?

I thought that I can rely on the origSpan and destSpan fields (If 0 - then number is internal otherwise, external), but I've lately encountered many cdrs that don't follow that rule.

Can anyone please explain how can I analyze the calls direction from the CDR fields?
Do I need to configure the Cisco Switch in a specific way?

Any help would be much appreciated,

Shira.

[kdotten36]

It sounds like you're trying to decipher the information from raw data.  If you're just looking for details on incoming and outgoing calls, go to Device Reports > Gateway > Detail and select the gateways/trunks you want to review.  If you're looking for call details (Internal & External) for a specific user, I've found the simplest layout under System Reports > QoS > Detail.  

[rosaho]

This discussion has been reposted to the IP Telephony community.

[shira.cohen1]

You are correct, we are working on the cdr raw data, but we have no access to the reports you mentioned, only the CDR files...

Thanks :)

[GaryB-UK]

Hi

When I look at Cisco CUCM CDR records to determine the direction of the call I will typically look at the calling and the called party numbers and particularly look at the length. This will not always work in every situation but generally internal ext numbers are shorter than the dialed numbers for offnet calls.

If the client uses a 4 digit ext range then you can do the following:

if callingpartynumber.length == 4 and originalcalledpartynumber == 4 (INTERNAL)

if callingpartynumber.length == 4 and originalcalledpartynumber.length > 4 (OUTBOUND)

if callingpartynumber.length > 4 and originalcalledpartynumber.length == 4 (INBOUND)

This will not work in all situations but might generally works for what I need so thought I would share.

Gary

[kdotten36]

side note: I stumbled onto this thread while researching how to generate a useful User Detail report.  Am I correct in stating there is no way for a user to generate a report that includes incoming calls without implementing a third-party or custom script?

[GaryB-UK]

I am not sure if there is a "inbound/outbound" flag, you could look at the "onnet/offnet" classification as that might give you what you need.

You could also look that the originating device (I think that is what it is called) as they may well show the ingress gateway and therefore the direction be determined from that

Gary

[kdotten36]

I'm actually referring to the reports a standard user can generate (under User Reports > Bills > Individual), not the raw CDR data.  You can see in the screenshot with the Individual compared to the QoS Detailed reports, the individual only contains calls placed from 7182, not received.

I didn't intend to hijack the thread though, I can look elsewhere.

[GaryB-UK]

Hi

I don't tend to look at the standard User reports in CUCM, I generally look at the raw CDR and then derive the direction based on client specific knowledge either length of ext or from the DDI range.

Gary

[shira.cohen1]

Thanks Gary for your reply :)

In our code that detects the call direction, we do look at the length of the number, but as you mentioned, there are many cases which that rule doesn't work...

We are also looking at the Partition fields, if they contain certain strings (e.g.: internal, line...), we assume that the party is an internal number, but that doesn't cover all call scenarios...