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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11849 
====================================================================== 
Reported By:                greyvoip
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   11849
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
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:             2008-01-26 11:11 CST
Last Modified:              2008-10-29 07:52 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 :).
====================================================================== 

---------------------------------------------------------------------- 
 (0094356) greyvoip (reporter) - 2008-10-29 07:52
 http://bugs.digium.com/view.php?id=11849#c94356 
---------------------------------------------------------------------- 
I checked out the latest 1.4 version from trunk, SVN-trunk-r152605, and the
blind transfer CDR is incorrect in the same way as 1.4.22, i.e.:

(A is a local Asterisk SIP user (non-billable call), B and C are PSTN
(billable calls)

1. A calls B and B answers,
2. A blind xfers B to C and C starts ringing,
3. C answers and B and C converse,
4. Call ends.

The CDRs generated are (same result as for 1.2 and 1.4.22):

1. B for 1 to 2,
2. C for 3 to 4.

-----------------------------------

I also checked out SVN-branch-1.4-r11885. For the blind transfer scenario
above the CDR results were:

1. B for 1 to 2,
2. C for 1 to 4.

This is different from any other version I've seen but is still not
correct. It did make me go back and check whether I had possibly misread
the call timings on 1.4.22 and/or 1.4 Trunk for the blind transfer CDRs but
I hadn't.

The CDRs should be:

1. B for 1 to 4,
2. C for 3 to 4.

In the case of SVN-branch-1.4-r11885 the first call leg (to B) will be
undercharged and the second call leg (to C) will be overcharged. From a
provider's point of view it's a philosophical question as to whether that's
better or worse than 1.4.22 where B is undercharged and C is correct.

Attended transfer CDRs were correct for SVN-branch-1.4-r11885. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-29 07:52 greyvoip       Note Added: 0094356                          
======================================================================