[asterisk-bugs] [Asterisk 0011849]: Missing CDR's for Transfers

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Jun 3 19:04:21 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=11849 
====================================================================== 
Reported By:                greyvoip
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   11849
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.17 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-01-26 11:11 CST
Last Modified:              2009-06-03 19:04 CDT
====================================================================== 
Summary:                    Missing CDR's for Transfers
Description: 
At the moment there is one CDR generated per generic bridge. This tends not
to create any problems when the bridge has been created by something like:

SIP User -> Asterisk -> PSTN

The CDR generated will have the PSTN number as the destination and the SIP
User's accountcode.

When a transfer is undertaken the one CDR per generic bridge approach
breaks down. An example call flow for a blind transfer is:

SIP User -> Asterisk -> PSTN
PSTN <- Asterisk -> PSTN (this is after the user has blind transferred the
first call to a second PSTN number)

At the moment Asterisk will correctly generate a CDR for the first call
leg but for the second call leg there is a problem. For the sconed call leg
both ends of the bridge are now billable but as Asterisk only generates a
single CDR per bridge one of the legs will not get billed. 

A straight forward fix (at least architecturally) would be to generate a
CDR for each end of the bridge instead of combining both ends into a single
CDR. It would mean some extra CDR's for the standard SIP User -> PSTN call
but it's a lot easier to filter out CDR's to ignore than it is to try and
work out how to handle ones that are missing.

I've classified this as major since it's costing me (and other providers)
money every time a user does a transfer :).
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013892 After upgrading from 1.4.21.2 to 1.4.22...
related to          0014398 Calls coming in then out do not get rec...
====================================================================== 

---------------------------------------------------------------------- 
 (0105964) sverre (reporter) - 2009-06-03 19:04
 https://issues.asterisk.org/view.php?id=11849#c105964 
---------------------------------------------------------------------- 
I can think of a few scenarios where having 1 CDR per channel would be
superior. Currently when one customer calls another customer on Asterisk,
the "incoming" CDR for the destination customer is missing (only 1 CDR to
share between two customers, and we'd rather keep the billable outgoing
one!).

That being said, I can't figure out in my mind how we would figure out
which channels are billable and which aren't - in most cases you'd only
want to bill for 1 of the 2, though I'm sure there'd be a way.

I'm going to say "yes it would resolve it", but I imagine there'd be quite
a process in figuring out how to implement a billing system around it.

Given that people can use my hack workaround to fix the problem for now,
my feeling is that any time spent fixing the current CDR system is time
that could be spent on the new CDR system, though it depends on how far off
it is. If we can expect to see it in the next month or so, I wouldn't worry
about it. If it's going to be 6 months on the other hand, then yes I'd
start playing with one CDR per channel. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-03 19:04 sverre         Note Added: 0105964                          
======================================================================




More information about the asterisk-bugs mailing list