[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:                     closed
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:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-01-26 11:11 CST
Last Modified:              2008-10-26 09:13 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 :).
====================================================================== 

---------------------------------------------------------------------- 
 (0094289) greyvoip (reporter) - 2008-10-26 09:13
 http://bugs.digium.com/view.php?id=11849#c94289 
---------------------------------------------------------------------- 
I've just got around to testing the transfer CDRs in 1.4.22 and there is
still a problem.

The problem below still occurs.

> The scenario that doesn't get recorded correctly is:
> 
> 1. A calls B.
> 2. A blind xfers B to C.
> 3. B and C converse...
> 4. Call ends.
>
> There are two CDRs we need from this call.
>
> 1. CDR for call to B of duration 1 to 4,
> 2. CDR for call to C from 2 to 4.
>
> The problem is with CDR 1 its duration is from 1 to 2. 

The situation for 1.4.22 and blind transfers is 

(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 by 1.4.22 are (same result as for 1.2):

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

The correct CDRs are:

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

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

Attended transfers are also back to being incorrect although they have
improved since earlier versions of 1.4.

The situation for 1.4.22 and attended transfers is:

(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 calls C and C answers,
3. A transfers B and C together,
4. Call ends.

The CDRs generated by 1.4.22 are:

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

The correct CDRs are:

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

The CDRs are likely to work out more expensive for providers than 1.2,
although once users work out the flaw it's easily exploited, which
produced:

1. B for 1 to 4,
2. B for 2 to 4 (B is not a typo).
 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-26 09:13 greyvoip       Note Added: 0094289                          
======================================================================