[asterisk-bugs] [Asterisk 0011093]: CDR Created incorrectly on Transfer of outgoing call

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11093 
====================================================================== 
Reported By:                rossbeer
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   11093
Category:                   Applications/app_cdr
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-26-2007 10:02 CDT
Last Modified:              02-26-2008 06:57 CST
====================================================================== 
Summary:                    CDR Created incorrectly on Transfer of outgoing call
Description: 
When making an outgoing call and then transferring a call to another
extension the CDR details are incorrect.

I would expect to see two CDR's created, one for the outgoing call and
another for the transfer as Asterisk does, however it stops (ends) the
outgoing CDR at the point of transfer, instead of continuing to increment
the 'seconds'.

This problem occurs on both blind transfers and attended (using a Snom and
not using '#' or '*1' features). However attended transfers are more
accurate than blind transfers, they do continue to count however the time
is not 100% accurate.

I have tried to fix this myself in the dial plan by using '/n' and a local
channel however it still occurs. This problem did not occur in previous
versions of Asterisk.
====================================================================== 

---------------------------------------------------------------------- 
 greyvoip - 02-26-08 06:57  
---------------------------------------------------------------------- 
Isn't the best starting point here to realise that both ends of an Asterisk
Call Bridge can change and there are always going to be instances where
both ends could be billable?

Adding in support for a few specific scenarios while more welcome than
nothing has the potential to create more problems than it solves as we have
seen from attended transfer CDRs from 1.2 to 1.4.

It's not so much the development work here but getting the design agreed
on. I still believe generating a CDR for each end of a call bridge is the
way to go. It means there can never be a situation where a call leg is not
recorded.

Thanks to you murf for looking into this. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-26-08 06:57  greyvoip       Note Added: 0082957                          
======================================================================