diff options
Diffstat (limited to 'doc')
-rw-r--r-- | doc/tex/asterisk.tex | 3 | ||||
-rw-r--r-- | doc/tex/cdrdriver.tex | 40 | ||||
-rw-r--r-- | doc/tex/cel-doc.tex | 8 | ||||
-rw-r--r-- | doc/tex/celdriver.tex | 36 | ||||
-rw-r--r-- | doc/tex/chan-mobile.tex (renamed from doc/tex/chan_mobile.tex) | 0 |
5 files changed, 44 insertions, 43 deletions
diff --git a/doc/tex/asterisk.tex b/doc/tex/asterisk.tex index 30f829c23..4934d14fc 100644 --- a/doc/tex/asterisk.tex +++ b/doc/tex/asterisk.tex @@ -8,6 +8,7 @@ \documentclass[12pt,a4]{report} \usepackage{hyperref} +\usepackage{underscore} \usepackage{url} \makeatletter @@ -100,7 +101,7 @@ reference purposes. \section{Local} \input{localchannel.tex} \section{Mobile} - \input{chan_mobile.tex} + \input{chan-mobile.tex} \chapter{Distributed Universal Number Discovery (DUNDi)} \section{Introduction} diff --git a/doc/tex/cdrdriver.tex b/doc/tex/cdrdriver.tex index 9a9337d5f..a94ddf28b 100644 --- a/doc/tex/cdrdriver.tex +++ b/doc/tex/cdrdriver.tex @@ -3,16 +3,16 @@ \subsection{Microsoft SQL Server} 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 Call Data Records can be stored using unixODBC (which requires - the FreeTDS package) [cdr\_odbc] or directly by using just the - FreeTDS package [cdr\_tds] The following provide some + the FreeTDS package) [cdr_odbc] or directly by using just the + FreeTDS package [cdr_tds] The following provide some examples known to get asterisk working with mssql. NOTE: Only choose one db connector. -\subsubsection{ODBC using cdr\_odbc} +\subsubsection{ODBC using cdr_odbc} Compile, configure, and install the latest unixODBC package: \begin{astlisting} \begin{verbatim} @@ -36,7 +36,7 @@ \end{astlisting} Compile, or recompile, asterisk so that it will now add support - for cdr\_odbc. + for cdr_odbc. \begin{astlisting} \begin{verbatim} make clean && ./configure --with-odbc && @@ -71,8 +71,8 @@ \end{astlisting} Only install one database connector. Do not confuse asterisk - by using both ODBC (cdr\_odbc) and FreeTDS (cdr\_tds). - This command will erase the contents of cdr\_tds.conf + by using both ODBC (cdr_odbc) and FreeTDS (cdr_tds). + This command will erase the contents of cdr_tds.conf \begin{astlisting} \begin{verbatim} [ -f /etc/asterisk/cdr_tds.conf ] > /etc/asterisk/cdr_tds.conf @@ -81,7 +81,7 @@ NOTE: unixODBC requires the freeTDS package, but asterisk does not call freeTDS directly. - Now set up cdr\_odbc configuration files. These are working samples + Now set up cdr_odbc configuration files. These are working samples from my system. You will need to modify for your setup. Define your usernames and passwords here, secure file as well. \begin{astlisting} @@ -121,7 +121,7 @@ logs a connection to the database and will now record every call to the database when it's complete. -\subsubsection{TDS, using cdr\_tds} +\subsubsection{TDS, using cdr_tds} Compile, configure, and install the latest FreeTDS package: \begin{astlisting} \begin{verbatim} @@ -133,7 +133,7 @@ \end{verbatim} \end{astlisting} Compile, or recompile, asterisk so that it will now add support - for cdr\_tds. + for cdr_tds. \begin{astlisting} \begin{verbatim} make clean && ./configure --with-tds && @@ -143,14 +143,14 @@ \end{verbatim} \end{astlisting} Only install one database connector. Do not confuse asterisk - by using both ODBC (cdr\_odbc) and FreeTDS (cdr\_tds). - This command will erase the contents of cdr\_odbc.conf + by using both ODBC (cdr_odbc) and FreeTDS (cdr_tds). + This command will erase the contents of cdr_odbc.conf \begin{astlisting} \begin{verbatim} [ -f /etc/asterisk/cdr_odbc.conf ] > /etc/asterisk/cdr_odbc.conf \end{verbatim} \end{astlisting} - Setup cdr\_tds configuration files. These are working samples + Setup cdr_tds configuration files. These are working samples from my system. You will need to modify for your setup. Define your usernames and passwords here, secure file as well. \begin{astlisting} @@ -199,13 +199,13 @@ \subsubsection{ODBC} -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. \subsubsection{Native} Alternatively, there is a native MySQL CDR module. -To use it, configure the module in cdr\_mysql.conf. Create a table called cdr under the database name you will be using the following schema. +To use it, configure the module in cdr_mysql.conf. Create a table called cdr under the database name you will be using the following schema. \begin{astlisting} \begin{verbatim} @@ -232,13 +232,13 @@ CREATE TABLE cdr ( \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. On Debian, before compiling asterisk, just install libpqxx-dev. Other distros will likely have a similiar package. Once you have the compile done, - copy the sample cdr\_pgsql.conf file or create your own. + copy the sample cdr_pgsql.conf file or create your own. Here is a sample: \begin{astlisting} @@ -280,11 +280,11 @@ CREATE TABLE cdr ( \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. +SQLite version 3 is supported in cdr_sqlite3\_custom. \subsection{RADIUS} @@ -475,7 +475,7 @@ SQLite version 3 is supported in cdr\_sqlite3\_custom. for all the fields which are recorded. By default, records in comma separated values will be created in \path{/var/log/asterisk/cdr-csv}. - The configuration file for cdr\_radius.so module is \path{/etc/asterisk/cdr.conf} + The configuration file for cdr_radius.so module is \path{/etc/asterisk/cdr.conf} This is where you can set CDR related parameters as well as the path to the radiusclient-ng library configuration file. diff --git a/doc/tex/cel-doc.tex b/doc/tex/cel-doc.tex index 03fea796f..dc007181a 100644 --- a/doc/tex/cel-doc.tex +++ b/doc/tex/cel-doc.tex @@ -831,8 +831,8 @@ correspond to the following two CDR records (at the moment!): While CDRs and the Manager are basically both event tracking mechanisms, CEL tries to track only those events that might pertain to billing issues. -See table~\ref{event_table} for a list of events raised by CEL and -table~\ref{field_table} for the list of fields passed for each CEL event. +See table~\ref{event-table} for a list of events raised by CEL and +table~\ref{field-table} for the list of fields passed for each CEL event. \begin{table}[h] \begin{tabular}{ | l | p{10cm} | } @@ -862,7 +862,7 @@ table~\ref{field_table} for the list of fields passed for each CEL event. \hline \end{tabular} \caption{List of CEL Events} - \label{event_table} + \label{event-table} \end{table} \begin{table}[h] @@ -890,7 +890,7 @@ table~\ref{field_table} for the list of fields passed for each CEL event. \hline \end{tabular} \caption{List of CEL Event Fields} - \label{field_table} + \label{field-table} \end{table} \section{Applications \& Functions} diff --git a/doc/tex/celdriver.tex b/doc/tex/celdriver.tex index 19224d674..c3abf0df0 100644 --- a/doc/tex/celdriver.tex +++ b/doc/tex/celdriver.tex @@ -7,16 +7,16 @@ for how to use these back ends. \subsection{Microsoft SQL Server} Asterisk can currently store Channel Events into an MSSQL database in - two different ways: cel\_odbc or cel\_tds + two different ways: cel_odbc or cel_tds Channel Event Records can be stored using unixODBC (which requires - the FreeTDS package) [cel\_odbc] or directly by using just the - FreeTDS package [cel\_tds] The following provide some + the FreeTDS package) [cel_odbc] or directly by using just the + FreeTDS package [cel_tds] The following provide some examples known to get asterisk working with mssql. NOTE: Only choose one db connector. -\subsubsection{ODBC using cel\_odbc} +\subsubsection{ODBC using cel_odbc} Compile, configure, and install the latest unixODBC package: \begin{verbatim} tar -zxvf unixODBC-2.2.9.tar.gz && @@ -36,7 +36,7 @@ for how to use these back ends. \end{verbatim} Compile, or recompile, asterisk so that it will now add support - for cel\_odbc. + for cel_odbc. \begin{verbatim} make clean && ./configure --with-odbc && make update && @@ -68,15 +68,15 @@ for how to use these back ends. \end{verbatim} Only install one database connector. Do not confuse asterisk - by using both ODBC (cel\_odbc) and FreeTDS (cel\_tds). - This command will erase the contents of cel\_tds.conf + by using both ODBC (cel_odbc) and FreeTDS (cel_tds). + This command will erase the contents of cel_tds.conf \begin{verbatim} [ -f /etc/asterisk/cel_tds.conf ] > /etc/asterisk/cel_tds.conf \end{verbatim} NOTE: unixODBC requires the freeTDS package, but asterisk does not call freeTDS directly. - Now set up cel\_odbc configuration files. These are working samples + Now set up cel_odbc configuration files. These are working samples from my system. You will need to modify for your setup. Define your usernames and passwords here, secure file as well. \begin{verbatim} @@ -113,7 +113,7 @@ for how to use these back ends. logs a connection to the database and will now record every desired channel event at the moment it occurs. -\subsubsection{FreeTDS, using cel\_tds} +\subsubsection{FreeTDS, using cel_tds} Compile, configure, and install the latest FreeTDS package: \begin{verbatim} tar -zxvf freetds-0.62.4.tar.gz && @@ -123,7 +123,7 @@ for how to use these back ends. make install \end{verbatim} Compile, or recompile, asterisk so that it will now add support - for cel\_tds. + for cel_tds. \begin{verbatim} make clean && ./configure --with-tds && make update && @@ -131,12 +131,12 @@ for how to use these back ends. make install \end{verbatim} Only install one database connector. Do not confuse asterisk - by using both ODBC (cel\_odbc) and FreeTDS (cel\_tds). - This command will erase the contents of cel\_odbc.conf + by using both ODBC (cel_odbc) and FreeTDS (cel_tds). + This command will erase the contents of cel_odbc.conf \begin{verbatim} [ -f /etc/asterisk/cel_odbc.conf ] > /etc/asterisk/cel_odbc.conf \end{verbatim} - Setup cel\_tds configuration files. These are working samples + Setup cel_tds configuration files. These are working samples from my system. You will need to modify for your setup. Define your usernames and passwords here, secure file as well. \begin{verbatim} @@ -178,16 +178,16 @@ for how to use these back ends. \subsection{MySQL} -Using MySQL for Channel Event records is supported by using ODBC and the cel\_odbc module. +Using MySQL for Channel Event records is supported by using ODBC and the cel_odbc module. \subsection{PostreSQL} - If you want to go directly to postgresql database, and have the cel\_pgsql.so + If you want to go directly to postgresql database, and have the cel_pgsql.so compiled you can use the following sample setup. On Debian, before compiling asterisk, just install libpqxx-dev. Other distros will likely have a similiar package. Once you have the compile done, - copy the sample cel\_pgsql.conf file or create your own. + copy the sample cel_pgsql.conf file or create your own. Here is a sample: \begin{verbatim} @@ -227,7 +227,7 @@ Using MySQL for Channel Event records is supported by using ODBC and the cel\_od \subsection{SQLite 3} -SQLite version 3 is supported in cel\_sqlite3\_custom. +SQLite version 3 is supported in cel_sqlite3_custom. \subsection{RADIUS} @@ -416,7 +416,7 @@ SQLite version 3 is supported in cel\_sqlite3\_custom. for all the fields which are recorded. By default, records in comma separated values will be created in /var/log/asterisk/cel-csv. - The configuration file for cel\_radius.so module is : + The configuration file for cel_radius.so module is : /etc/asterisk/cel.conf This is where you can set CEL related parameters as well as the path to diff --git a/doc/tex/chan_mobile.tex b/doc/tex/chan-mobile.tex index 09a95c75d..09a95c75d 100644 --- a/doc/tex/chan_mobile.tex +++ b/doc/tex/chan-mobile.tex |