[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 10:06 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 ...
====================================================================== 

---------------------------------------------------------------------- 
 deeperror - 06-13-08 10:06  
---------------------------------------------------------------------- 
nullok is unrelated to this issue.

Output CDR's seems find as i'm now getting both legs of the call in
Master.csv.  

In our environment the only time i'm seeing "No Answer Time" is when an
outbound call occurs and no one answers.  So from what I see the warning
doesn't need to be there.  

What is a timeline or how long would a fix like this take to get into
stable release? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-13-08 10:06  deeperror      Note Added: 0088669                          
======================================================================