[asterisk-commits] seanbright: branch group/newcdr r202645 - /team/group/newcdr/doc/tex/

[SVN commits to the Asterisk project]

Author: seanbright
Date: Tue Jun 23 10:42:47 2009
New Revision: 202645

URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=202645
Log:
Add the CEL documents to asterisk.tex and fix a few errors in the markup.

Modified:
    team/group/newcdr/doc/tex/asterisk.tex
    team/group/newcdr/doc/tex/cel-doc.tex

Modified: team/group/newcdr/doc/tex/asterisk.tex
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/newcdr/doc/tex/asterisk.tex?view=diff&rev=202645&r1=202644&r2=202645
==============================================================================
--- team/group/newcdr/doc/tex/asterisk.tex (original)
+++ team/group/newcdr/doc/tex/asterisk.tex Tue Jun 23 10:42:47 2009
@@ -117,6 +117,10 @@
 \input{billing.tex}
 \input{cdrdriver.tex}
 
+\chapter{CEL: Channel Event Logging}
+\input{cel-doc.tex}
+\input{celdriver.tex}
+
 \chapter{Voicemail}
   \section{ODBC Storage}
   \label{odbcstorage}

Modified: team/group/newcdr/doc/tex/cel-doc.tex
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/newcdr/doc/tex/cel-doc.tex?view=diff&rev=202645&r1=202644&r2=202645
==============================================================================
--- team/group/newcdr/doc/tex/cel-doc.tex (original)
+++ team/group/newcdr/doc/tex/cel-doc.tex Tue Jun 23 10:42:47 2009
@@ -1,5 +1,5 @@
 
-\section(Design Goals)
+\section{Design Goals}
 
 CEL is being written with the hopes that it will help solve some of the problems
 that were difficult to address in CDR records. Some difficulties in CDR generation
@@ -18,7 +18,7 @@
 which basically provides a communication channel between two communication ports. It makes
 sense to have an event system aimed at recording important events on channels. Each
 Event is attached to a channel, like ANSWER or HANGUP. Some events are meant to connect
-two or more channels, like the BRIDGE_START event. Some events, like BLINDTRANSFER, are initiated
+two or more channels, like the BRIDGE\_START event. Some events, like BLINDTRANSFER, are initiated
 by one channel, but affect two others. These events use the Peer field, like BRIDGE would,
 to point to the target channel.
 
@@ -763,7 +763,7 @@
 \end{verbatim}
 
 
-\section(CEL Events and Fields)
+\section{CEL Events and Fields}
 
 While CDR's and the Manager are basically both event tracking mechanisms, CEL tries
 to track only those events that might pertain to billing issues.
@@ -816,7 +816,7 @@
 \end{verbatim}
 
 
-\section(CEL Applications, Functions)
+\section{CEL Applications, Functions}
 
 \subsection{The CEL Function}
 
@@ -833,7 +833,7 @@
 
 See the description for the CEL function from the CLI: core show function CEL
 
-Here is a list of all the available channel field names:\n"
+Here is a list of all the available channel field names:
 \begin{verbatim}
     cidname       userfield
     cidnum        amaflags
@@ -863,14 +863,14 @@
 a blessing or a curse!
 
 
-\section(CEL config files)
-
-\section(CEL Back Ends)
+\section{CEL config files}
+
+\section{CEL Back Ends}
 
 Right now, the CEL package will support CSV, Customized CSV, ODBC, PGSQL, TDS, Sqlite, Sqlite3, and Radius database backends.
 See the doc/celdriver.tex file for how to use these back ends.
 
-\section(Generating Billing Information)
+\section{Generating Billing Information}
 
 ** this is the Next Big Task ***