[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 09:16 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 09:16  
---------------------------------------------------------------------- 
The "No answer tune" is a typo; I corrected it to say "No answer time"
instead.
The code that generates this message is kinda new to the CDRfix4/5/6 set,
and it may or may not be meaningful. For instance, if the disposition is
NO_ANSWER, then not having an answer time is no crime. I can arrange to
make the warning more relevant, or remove it altogether if in the end, the
CDR's are what we would expect. 


As to the nullok message, I have no idea what the problem is. Any guess I
might make to explain it would be pure conjecture. If your Zap channels are
working as expected, you might be able to ignore it. Sometimes the guys
working on the channel drivers throw in diagnostics, and don't get to test
it with the all the common scenarios. If enough people complain they are
seeing this diagnostic message, and there aren't any real problems, they
get tired of the questions, and remove the diagnostic.

So, if we ignore these diagnostics for the moment, what about the output
CDR's? Are they OK? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-13-08 09:16  murf           Note Added: 0088668                          
======================================================================