[svn-commits] seanbright: trunk r202841 - in /trunk/doc/tex: billing.tex cdrdriver.tex

[SVN commits to the Digium repositories]

Author: seanbright
Date: Tue Jun 23 18:57:07 2009
New Revision: 202841

URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=202841
Log:
Change some section names in the CDR tex documentation.

Modified:
    trunk/doc/tex/billing.tex
    trunk/doc/tex/cdrdriver.tex

Modified: trunk/doc/tex/billing.tex
URL: http://svn.asterisk.org/svn-view/asterisk/trunk/doc/tex/billing.tex?view=diff&rev=202841&r1=202840&r2=202841
==============================================================================
--- trunk/doc/tex/billing.tex (original)
+++ trunk/doc/tex/billing.tex Tue Jun 23 18:57:07 2009
@@ -15,7 +15,7 @@
 You can set default account codes and AMA flags for devices in
 channel configuration files, like sip.conf, iax.conf etc.
 
-\section{Fields of the CDR in Asterisk}
+\section{CDR Fields}
 
 \begin{itemize}
    \item accountcode:  What account number to use, (string, 20 characters)
@@ -53,11 +53,11 @@
 (although this can result in a media latency increase since the media packets
 have to traverse the middle server(s) in the call).
 
-\section{CDR Variables}
+\section{Variables}
 
-If the channel has a cdr, that cdr record has its own set of variables which
-can be accessed just like channel variables. The following builtin variables
-are available.
+If the channel has a CDR, that CDR has its own set of variables which can be
+accessed just like channel variables. The following builtin variables are
+available.
 
 \begin{verbatim}
 ${CDR(clid)}         Caller ID

Modified: trunk/doc/tex/cdrdriver.tex
URL: http://svn.asterisk.org/svn-view/asterisk/trunk/doc/tex/cdrdriver.tex?view=diff&rev=202841&r1=202840&r2=202841
==============================================================================
--- trunk/doc/tex/cdrdriver.tex (original)
+++ trunk/doc/tex/cdrdriver.tex Tue Jun 23 18:57:07 2009
@@ -1,6 +1,6 @@
-\section{CDR Back Ends}
-
-\subsection{MSSQL}
+\section{Storage Backends}
+
+\subsection{Microsoft SQL Server}
 
 	Asterisk can currently store CDRs into an MSSQL database in
 	two different ways:  cdr\_odbc or cdr\_tds
@@ -195,11 +195,11 @@
                 call to the database when it's complete.
 
 
-\subsection{MYSQL}
+\subsection{MySQL}
 
 Using MySQL for CDR records is supported by using ODBC and the cdr\_odbc module.
 
-\subsection{PGSQL}
+\subsection{PostgreSQL}
         If you want to go directly to postgresql database, and have the cdr\_pgsql.so
         compiled you can use the following sample setup.
         On Debian, before compiling asterisk, just install libpqxx-dev.
@@ -246,9 +246,13 @@
 \end{verbatim}
 \end{astlisting}
 
-\subsection{SQLLITE}
+\subsection{SQLite 2}
 
 SQLite version 2 is supported in cdr\_sqlite.
+
+\subsection{SQLite 3}
+
+SQLite version 3 is supported in cdr\_sqlite3\_custom.
 
 \subsection{RADIUS}