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

[Asterisk Bug Tracker]

The following issue is now READY FOR TESTING. 
====================================================================== 
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:                     ready for testing
Asterisk Version:           1.4.20 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-06-28 20:50 CDT
Last Modified:              2009-02-06 12:30 CST
====================================================================== 
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.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013892 After upgrading from 1.4.21.2 to 1.4.22...
====================================================================== 

---------------------------------------------------------------------- 
 (0099636) murf (administrator) - 2009-02-06 12:30
 http://bugs.digium.com/view.php?id=12946#c99636 
---------------------------------------------------------------------- 
Earlier, I said (and I quote)

"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. "

Well, I sat down and thought about the current criteria, and 
made mods to chan_dahdi and app_dial for 13892; I've been busy testing
them under
different conditions.

Probably similar changes will have to be done for other channel drivers,
we'll see. I eliminated disposition entirely as a condition for posting a
CDR, in favor of the dstchannel being set.
I cleaned up the publishing of peer dial attempts when unanswered=yes. And
when unanswered=no, you get every dial attempt. Dial will now reset any
disposition and answer times as it is starting, just in case a previous
Answer() was performed. The result is that you see your 3 CDR's no matter
the call disposition in every case. I'll be checking that chan_sip is doing
the right thing later today.

If you can't test this with dahdi (analog) phones or t1/pri type phones,
then wait I check the sip stuff, probably later today.
 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-06 12:30 murf           Note Added: 0099636                          
2009-02-06 12:30 murf           Status                   feedback => ready for
testing
======================================================================