diff options
author | seanbright <seanbright@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-06-23 23:57:07 +0000 |
---|---|---|
committer | seanbright <seanbright@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-06-23 23:57:07 +0000 |
commit | 59155c3ce5bb66d9f41b8562dd41373c4f8ba58f (patch) | |
tree | 330947f5089ada765807d703fab45dfb809336fd /doc | |
parent | 8b94aa5d84b258537197c5b7cd74d704455d86b0 (diff) |
Change some section names in the CDR tex documentation.
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@202841 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc')
-rw-r--r-- | doc/tex/billing.tex | 10 | ||||
-rw-r--r-- | doc/tex/cdrdriver.tex | 14 |
2 files changed, 14 insertions, 10 deletions
diff --git a/doc/tex/billing.tex b/doc/tex/billing.tex index 9fae40be8..5c7f68a60 100644 --- a/doc/tex/billing.tex +++ b/doc/tex/billing.tex @@ -15,7 +15,7 @@ For more information, use the "core show application $<$application$>$" command. 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 @@ transfers with IAX2 to avoid this problem, or turn off transfers completely (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 diff --git a/doc/tex/cdrdriver.tex b/doc/tex/cdrdriver.tex index ad5a8a20d..3fe7e148b 100644 --- a/doc/tex/cdrdriver.tex +++ b/doc/tex/cdrdriver.tex @@ -1,6 +1,6 @@ -\section{CDR Back Ends} +\section{Storage Backends} -\subsection{MSSQL} +\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,10 +246,14 @@ Using MySQL for CDR records is supported by using ODBC and the cdr\_odbc module. \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} \subsubsection{What is needed} |