kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-09-30 02:26:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Change some section names in the CDR tex documentation.

Browse Source 
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@202841 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Sean Bright
2009-06-23 23:57:07 +00:00
parent 233f1bc8da
commit 5059530d62
2 changed files with 14 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/tex/billing.tex
View File

@@ -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 You can set default account codes and AMA flags for devices in
channel configuration files, like sip.conf, iax.conf etc. channel configuration files, like sip.conf, iax.conf etc.
\section{Fields of the CDR in Asterisk} \section{CDR Fields}
\begin{itemize} \begin{itemize}
\item accountcode: What account number to use, (string, 20 characters) \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 (although this can result in a media latency increase since the media packets
have to traverse the middle server(s) in the call). 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 If the channel has a CDR, that CDR has its own set of variables which can be
can be accessed just like channel variables. The following builtin variables accessed just like channel variables. The following builtin variables are
are available. available.
\begin{verbatim} \begin{verbatim}
${CDR(clid)} Caller ID ${CDR(clid)} Caller ID

14
doc/tex/cdrdriver.tex
View File

@@ -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 Asterisk can currently store CDRs into an MSSQL database in
two different ways: cdr\_odbc or cdr\_tds two different ways: cdr\_odbc or cdr\_tds
@@ -195,11 +195,11 @@
call to the database when it's complete. 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. 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 If you want to go directly to postgresql database, and have the cdr\_pgsql.so
compiled you can use the following sample setup. compiled you can use the following sample setup.
On Debian, before compiling asterisk, just install libpqxx-dev. 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{verbatim}
\end{astlisting} \end{astlisting}
\subsection{SQLLITE} \subsection{SQLite 2}
SQLite version 2 is supported in cdr\_sqlite. SQLite version 2 is supported in cdr\_sqlite.
\subsection{SQLite 3}
SQLite version 3 is supported in cdr\_sqlite3\_custom.
\subsection{RADIUS} \subsection{RADIUS}
\subsubsection{What is needed} \subsubsection{What is needed}