[asterisk-bugs] [Asterisk 0010659]: CDRs are not merged for not answered calls

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10659 
====================================================================== 
Reported By:                casper
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   10659
Category:                   CDR/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-06-2007 10:02 CDT
Last Modified:              11-27-2007 00:57 CST
====================================================================== 
Summary:                    CDRs are not merged for not answered calls
Description: 
After upgrade from 1.2 to 1.4 I noticed that bogus CDRs were generated for
timed out or cancelled calls with context "default" and extention "s".
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0011379 1.4.14 breaks cdr posting
====================================================================== 

---------------------------------------------------------------------- 
 murf - 11-27-07 00:57  
---------------------------------------------------------------------- 
I set up an option for 11379, that lets you choose whether you want to see
the extra CDR's. (by default, you won't see the extra unanswered cdrs.).

Either way, no more pesky "cdr not posted" messages.

I basically put code into app_dial to disable posting the rung channels if
the option isn't set. That's a better place, as we know the intention of
the channel there.

I'll leave this open for a little while.  Did my fix to 11379 solve this
problem? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-27-07 00:57  murf           Note Added: 0074385                          
======================================================================