[asterisk-bugs] [Asterisk 0017334]: CDR bug w/ r258670 on

Asterisk Bug Tracker noreply at bugs.digium.com
Thu May 13 13:42:21 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17334 
====================================================================== 
Reported By:                jvandal
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17334
Category:                   CDR/General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.32-rc1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 262898 
Request Review:              
====================================================================== 
Date Submitted:             2010-05-13 11:26 CDT
Last Modified:              2010-05-13 13:42 CDT
====================================================================== 
Summary:                    CDR bug w/ r258670 on
Description: 
The following changes on 1.4 SVN cause lots of problems ...

By sample, I dial a Queue (ACD) and hangup ... I have an ABANDON event on
Queue Log but no CDR records.

If I enable 'unanswered=yes' on cdr.conf, now I have CDR ...

------------------------------------------------------------------------
r258670 | mnicholson | 2010-04-22 17:49:07 -0400 (Thu, 22 Apr 2010) | 11
lines

Fix broken CDR behavior.

This change allows a CDR record previously marked with disposition
ANSWERED to be set as BUSY or NO ANSWER.

Additionally this change partially reverts r235635 and does not set the
AST_CDR_FLAG_ORIGINATED flag on CDRs
generated from ast_call().  To preserve proper CDR behavior, the
AST_CDR_FLAG_DIALED flag is now cleared from
all brige CDRs in ast_bridge_call().

(closes issue https://issues.asterisk.org/view.php?id=16797)
Reported by: VarnishedOtter
Tested by: mnicholson


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

---------------------------------------------------------------------- 
 (0121887) aragon (reporter) - 2010-05-13 13:42
 https://issues.asterisk.org/view.php?id=17334#c121887 
---------------------------------------------------------------------- 
developer:
Here is my dilemna:
Unless I write
cdr.conf
unanswered=yes

Then no abandoned event is written to CDR and no caller ID is captured and
written to CDR.
If unanswered=yes then still no event is written to CDR for answered or
overflow events such as exitfull exitwithtimeout exitempty
exitwithkeypress
queue_log captures events OK.  But queue CDR events are completely
broken.
I have to downgrade to 1.4.30 to fix. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-13 13:42 aragon         Note Added: 0121887                          
======================================================================




More information about the asterisk-bugs mailing list