[asterisk-bugs] [Asterisk 0010927]: Zap assisted xfer via hookflash yield CDR errors and bad CDR's.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10927 
====================================================================== 
Reported By:                murf
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   10927
Category:                   CDR/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.12.1  
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-09-2007 11:14 CDT
Last Modified:              06-13-2008 11:13 CDT
====================================================================== 
Summary:                    Zap assisted xfer via hookflash yield CDR errors and
bad CDR's.
Description: 
While most assisted xfer scenarios seem to work OK
within chan_zap, one sequence has CDR problems.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0011093 CDR Created incorrectly on Transfer of ...
====================================================================== 

---------------------------------------------------------------------- 
 murf - 06-13-08 11:13  
---------------------------------------------------------------------- 
Well, since this set of fixes is aimed at closing several bug reports,
it would be good to have a good amount of feedback. For instance, I've
been hearing a lot of noise about dropped accountcodes... is that still a
problem?

Another fly in the ointment is that I plan to svnmerge in the dahdi 
code today, which will trade the zap for dahdi names, which shouldn't 
make any difference, but... you never know.

I do have some requests to fix the CDR generation for things like
attended xfers, to generate 3 CDR's instead of 2. But I need some sort
of agreement about how the 3rd CDR should appear.  I've been thinking
on it, and the transferer should be the originator, even if he didn't
participate in the call, because he's the one that dialed it. So, if
he transfers the call to a long-distance external number, he should most
likely get assigned the $400 expense. Perhaps the lastapp could be
'xfer',
and the lastdata could indicate that he transferred the call to "Zap/11"
or somesuch... at any rate, such structural changes to the way CDR's are
getting generated will most likely not be welcome in 1.4, but depending
on who you talk to, it could either be considered an enhancement or a bug
fix.
In such cases, I'd have to go with the guys whose apps would be broken,
and call it an enhancement, and intro it in trunk for the next 1.6
release.
What do you-all think? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-13-08 11:13  murf           Note Added: 0088674                          
======================================================================