diff options
author | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-06-23 22:47:48 +0000 |
---|---|---|
committer | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-06-23 22:47:48 +0000 |
commit | 377fca7c1655654acc43bc436763797da3a390ef (patch) | |
tree | e3bbb19ed97a925e6b451f6a18e40b0235f3f8bc /doc | |
parent | e41ab93841a1f75dea5413b62b5e359ae44a2c6c (diff) |
Merged revisions 202804 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk
........
r202804 | russell | 2009-06-23 17:47:26 -0500 (Tue, 23 Jun 2009) | 2 lines
Clean up section hierarchy for the CDR chapter.
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.2@202805 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc')
-rw-r--r-- | doc/tex/cdrdriver.tex | 22 |
1 files changed, 10 insertions, 12 deletions
diff --git a/doc/tex/cdrdriver.tex b/doc/tex/cdrdriver.tex index b6e122d7b..2937fc9fc 100644 --- a/doc/tex/cdrdriver.tex +++ b/doc/tex/cdrdriver.tex @@ -1,6 +1,6 @@ -Call data records can be stored in many different databases or even CSV text. +\section{CDR Back Ends} -\section{MSSQL} +\subsection{MSSQL} Asterisk can currently store CDRs into an MSSQL database in two different ways: cdr\_odbc or cdr\_tds @@ -12,7 +12,7 @@ Call data records can be stored in many different databases or even CSV text. NOTE: Only choose one db connector. -\subsection{ODBC using cdr\_odbc} +\subsubsection{ODBC using cdr\_odbc} Compile, configure, and install the latest unixODBC package: \begin{astlisting} \begin{verbatim} @@ -121,7 +121,7 @@ Call data records can be stored in many different databases or even CSV text. logs a connection to the database and will now record every call to the database when it's complete. -\subsection{TDS, using cdr\_tds} +\subsubsection{TDS, using cdr\_tds} Compile, configure, and install the latest FreeTDS package: \begin{astlisting} \begin{verbatim} @@ -195,11 +195,11 @@ Call data records can be stored in many different databases or even CSV text. call to the database when it's complete. -\section{MYSQL} +\subsection{MYSQL} Using MySQL for CDR records is supported by using ODBC and the cdr\_odbc module. -\section{PGSQL} +\subsection{PGSQL} 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,13 +246,13 @@ Using MySQL for CDR records is supported by using ODBC and the cdr\_odbc module. \end{verbatim} \end{astlisting} -\section{SQLLITE} +\subsection{SQLLITE} SQLite version 2 is supported in cdr\_sqlite. -\section{RADIUS} +\subsection{RADIUS} -\subsection{What is needed} +\subsubsection{What is needed} \begin{itemize} \item FreeRADIUS server @@ -289,8 +289,6 @@ SQLite version 2 is supported in cdr\_sqlite. \caption{Asterisk/RADIUS Integration} \end{figure} -\subsection{Steps to follow in order to have RADIUS support} - \subsubsection{Installation of the Radiusclient library} Download the sources from @@ -447,7 +445,7 @@ SQLite version 2 is supported in cdr\_sqlite. the radiusclient-ng library configuration file. -\section{Logged Values} +\subsubsection{Logged Values} \begin{verbatim} "Asterisk-Acc-Code", The account name of detail records "Asterisk-Src", |