[asterisk-bugs] [Asterisk 0012946]: ResetCDR not work now on non-answered channel

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12946 
====================================================================== 
Reported By:                meral
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   12946
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.20 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-06-28 20:50 CDT
Last Modified:              2008-09-10 22:53 CDT
====================================================================== 
Summary:                    ResetCDR not work now on non-answered channel
Description: 
i am using resetCDR(w) for re-setup cdr and post prevous one
when channel is answered, resetCDr(w) works as documented
so:
exten =>s,1,Answer
exten =>s,n,ResetCDR(w)
exten =>s,n,ResetCDR(w)
produce 3 records
but if channel unanswered,then
exten =>s,1,ResetCDR(w)
exten =>s,n,ResetCDR(w)
produce only 1 record.

====================================================================== 

---------------------------------------------------------------------- 
 (0092329) murf (administrator) - 2008-09-10 22:53
 http://bugs.digium.com/view.php?id=12946#c92329 
---------------------------------------------------------------------- 
OK, I've labbed this one up, and ran it thru tests.

These are single-channel CDR's, and are affected by the 
unanswered = no
declaration in cdr.conf

if you remove that, or change it to unanswered = yes in cdr.conf,
you'll see all the Reset() cdrs, whether answer() was called or
not.

To be totally truthful, it wouldn't hurt us to sit down and 
come up with better criteria as to which CDR's are useful and
which are not. Right now, my personal feeling is that the criteria
for filtering single-channel CDR's is rather shaky. Stuff like
only IVR-answered incoming calls are useful and should end up in the CDR 
record, but the unanswered=no was meant to filter out the unanswered
channels that happen when Dial calls multiple lines at once, where one
wins, but the others are dropped.

Perhaps it is time to re-evaluate this entire situation and come up with
a spec that everyone can live with. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-10 22:53 murf           Note Added: 0092329                          
======================================================================