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

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11849 
====================================================================== 
Reported By:                greyvoip
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11849
Category:                   Core-General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-26-2008 11:11 CST
Last Modified:              01-29-2008 14:32 CST
====================================================================== 
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 :).
====================================================================== 

---------------------------------------------------------------------- 
 greyvoip - 01-29-08 14:32  
---------------------------------------------------------------------- 
There's no way you could tell from the lastdata field on a blind transfer
CDR whether the call was part of a transfer or not. Perhaps you could do
something tricky by dropping the call into the TRANSFER_CONTEXT and
recording the first call leg destination in the CDRUserField. It's a bit of
a hack though and will only work for blind transfers. For attended
transfers you can't use that approach.

Aside from that it's not so much the there may be a work around for this
case and that case the point is the CDR's being generated are incorrect.
Isn't the best idea to correct them? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-29-08 14:32  greyvoip       Note Added: 0081364                          
======================================================================