[asterisk-commits] murf: branch group/CDRfix5 r75033 - /team/group/CDRfix5/doc/tex/cdrbible.tex

[SVN commits to the Asterisk project]

Author: murf
Date: Fri Jul 13 09:43:09 2007
New Revision: 75033

URL: http://svn.digium.com/view/asterisk?view=rev&rev=75033
Log:
Checking in a little more

Modified:
    team/group/CDRfix5/doc/tex/cdrbible.tex

Modified: team/group/CDRfix5/doc/tex/cdrbible.tex
URL: http://svn.digium.com/view/asterisk/team/group/CDRfix5/doc/tex/cdrbible.tex?view=diff&rev=75033&r1=75032&r2=75033
==============================================================================
--- team/group/CDRfix5/doc/tex/cdrbible.tex (original)
+++ team/group/CDRfix5/doc/tex/cdrbible.tex Fri Jul 13 09:43:09 2007
@@ -333,13 +333,25 @@
 
 \subsection{Suppressing Asterisk-Generated CDRs}
 
-More to come.
+The application NoCDR() is available to set a flag in the current channel's CDR.
+This must be called before a bridge is started. The bridgeing code will check
+this flag before setting a CDR, and none will be tracked or posted.
+
+If you completely want to turn off the internal CDR generating mechanism, so you can
+use CDR_CONTROL to generate your own (completely), then you'll need to use NoCDR
+in all contexts and extensions where CDR's might be generated. This includes those
+contexts and extensions where transfers might be originated from.
+
+If you wish to completely shut all CDR generation, then you might just turn off
+the CDR facility entirely in the cdr.conf file.
 
 \subsection{Gotchas and Complications}
 
-What happens in transfers.
+What happens in transfers. More to come.
+
 
 \subsection{Backend Mappings}
+
 Here is a short snippet I spotted on IRC, in #asterisk, just this morning.(I changed the names).
 \begin{verbatim}
 X: Y, also, can't you use cdr_tds for mssql?
@@ -355,6 +367,5 @@
 be glad you did. Plus, the cdr_adaptive_odbc offers some advantages (at the moment) that other
 databases don't offer: complete mappings.
 
-
-
-
+More to come.
+