[asterisk-bugs] [Asterisk 0016180]: [patch] CDR dispositions BUSY and FAILED are reported as NO ANSWER

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Dec 18 16:29:54 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16180 
====================================================================== 
Reported By:                aatef
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   16180
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Target Version:             1.4.29
Asterisk Version:           SVN 
JIRA:                       SWP-362 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-04 13:04 CST
Last Modified:              2009-12-18 16:29 CST
====================================================================== 
Summary:                    [patch] CDR dispositions BUSY and FAILED are
reported as NO ANSWER
Description: 
Asterisk 1.4.26.2 and I think all Asterisk versions after 1.4.20 all report
the calls with Disposition BUSY and FAILED as NO ANSWER calls.
So in the CDR there are only 2 DISPOSITIONS available ANSWER and NO ANSWER
only


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012946 [patch] ResetCDR does not work on non-a...
====================================================================== 

---------------------------------------------------------------------- 
 (0115438) svnbot (reporter) - 2009-12-18 16:29
 https://issues.asterisk.org/view.php?id=16180#c115438 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 235635

U   branches/1.4/include/asterisk/cdr.h
U   branches/1.4/main/channel.c

------------------------------------------------------------------------
r235635 | jpeeler | 2009-12-18 16:29:52 -0600 (Fri, 18 Dec 2009) | 48
lines

Correct CDR dispositions for BUSY/FAILED

This patch is simple in that it reorders the disposition defines so that
the fix
for issue 12946 works properly (the default CDR disposition was changed to
AST_CDR_NOANSWER). Also, the AST_CDR_FLAG_ORIGINATED flag was set in
ast_call to
ensure all CDR records are written.

The side effects of CDR changes are scary, so I'm documenting the test
cases
performed to attempt to catch any regressions. The following tests were
all
performed using 1.4 rev 195881 vs head (235571) + patch:

A calls B
C calls B (busy)
Hangup C
Hangup A

(Both SIP and features)
A calls B
A blind transfers to C
Hangup C

(Both SIP and features)
A calls B
A attended transfers to C
Hangup C

A calls B
A attended transfers to C (SIP)
C blind transfers to A (features)
Hangup A

All of the test scenario CDRs matched.

The following tests were performed just with the patch to ensure proper
operation
(with unanswered=yes):

exten =>s,1,Answer
exten =>s,n,ResetCDR(w)
exten =>s,n,ResetCDR(w)

exten =>s,1,ResetCDR(w)
exten =>s,n,ResetCDR(w)

(closes issue https://issues.asterisk.org/view.php?id=16180)
Reported by: aatef
Patches: 
      bug16180.patch uploaded by jpeeler (license 325)

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=235635 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-18 16:29 svnbot         Note Added: 0115438                          
======================================================================




More information about the asterisk-bugs mailing list