[asterisk-bugs] [Asterisk 0011643]: Allow for the conditional logging of CDRs based on call disposition

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11643 
====================================================================== 
Reported By:                kratzers
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   11643
Category:                   CDR/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 94974 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-27-2007 13:52 CST
Last Modified:              03-21-2008 02:02 CDT
====================================================================== 
Summary:                    Allow for the conditional logging of CDRs based on
call disposition
Description: 
In our setting, we've found it desirable to log CDRs conditionally based on
the call disposition. For instance, only log CDRs for calls that were
either answered or not answered. Attached is a patch which allows users to
specify the dispositions to log using a mask (inverse) such as
NOANSWER|ANSWERED. The default is to log everything:
FAILED|BUSY|NOANSWER|ANSWERED.

Note: This serves a different purpose than "unanswered" and, for this
purpose, is much more granular.
====================================================================== 

---------------------------------------------------------------------- 
 juggie - 03-21-08 02:02  
---------------------------------------------------------------------- 
I agree w/ qwell i'm not sure i see the point, you can easily filter the
records you want with any of the backends.  The only situation i can see
this being of any use in would be be the cdr_manager backend.  In that
situation you may only want to see manager events for certain types of
cdr's.  Besides that i dont see why you cannot filter at the destination. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-21-08 02:02  juggie         Note Added: 0084382                          
======================================================================