Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CDR error

Hi ,

I?m responsible for billing solution.

The problem that we have in the billing solution, is when we start query to have a report for an internal calls, we have a result that many external calls are considered like a local calls.

We asked the question to billing solution support and after he see the CDR, he told us that:

The reason is that for an unknown reason (relative to the programming of the CCM and/or footbridges), the two IP addresses of the footbridges by which pass the origin call and of the named are equal to zero in the CDR, precisely as for a true internal call

Example:

1,2,41287,33650297,1154019016,2,0,-1977610068,,9066,0,0,-1977610068,16384,4,20,0,33650307,2,0,-48230228,,068099826,068099826,0,0,-48230228,18530,4,20,0,1154019016,1154062218,5010,Acc_Nat_STD,Phones,Acc_Nat_STD,Profiles,43202,SEP0017592EF949,AALN/S0/SU1/3@R2801,0,4,0,0,13,0,10,StandAloneCluster,10,4,0,0,0,0,0,4,0,0,0,0,0,,,,,0,

In this example, the data Incoming Trunk and Outgoing Trunk are present in the fields 7 and 20.

I make you join in attachment an example of the CDRs where I? specified:

origSpan, destSpan and lastRedirectDn :

 When we have an internal call (like 9 * * *---> 9 * * *) we have [origSpan=destSpan=0] and it is correct.

 But there are some calls toward the outside example: [9004---> 61155155] [origSpan=destSpan=0] and it is not correct (all model in red).

 In the model in green the external calls where [(origSpan= 0) # (destSpan)] and it is correct.

We want to know why these external calls are considered like internal calls. And how to solve this problem?

106
Views
0
Helpful
0
Replies
CreatePlease login to create content