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

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
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:                     closed
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:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             12-27-2007 13:52 CST
Last Modified:              04-30-2008 09:47 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.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 04-30-08 09:47  
---------------------------------------------------------------------- 
It's actually different from spam filtering.  CDRs are logs, and as a
system administrator, you never try to filter just the messages you think
are important; you log the general cases, and filter out the messages you
don't want afterwards.  You never want to be in the situation where you
have failed to log enough information.  Too much is always better than too
little.

Closing, as requested. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-30-08 09:47  Corydon76      Note Added: 0086201                          
04-30-08 09:47  Corydon76      Status                   assigned => closed  
04-30-08 09:47  Corydon76      Resolution               open => won't fix   
======================================================================