[asterisk-commits] russell: branch group/newcdr r202797 - /team/group/newcdr/doc/tex/
SVN commits to the Asterisk project
asterisk-commits at lists.digium.com
Tue Jun 23 17:27:44 CDT 2009
Author: russell
Date: Tue Jun 23 17:27:39 2009
New Revision: 202797
URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=202797
Log:
Minor spelling/grammatical changes, clean up section hierarchy
Modified:
team/group/newcdr/doc/tex/cel-doc.tex
team/group/newcdr/doc/tex/celdriver.tex
Modified: team/group/newcdr/doc/tex/cel-doc.tex
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/newcdr/doc/tex/cel-doc.tex?view=diff&rev=202797&r1=202796&r2=202797
==============================================================================
--- team/group/newcdr/doc/tex/cel-doc.tex (original)
+++ team/group/newcdr/doc/tex/cel-doc.tex Tue Jun 23 17:27:39 2009
@@ -1,7 +1,7 @@
\section{Design Goals}
-CEL, or Channel Event Logging, is being written with the hopes that it will help
+CEL, or Channel Event Logging, has been written with the hopes that it will help
solve some of the problems that were difficult to address in CDR records. Some
difficulties in CDR generation are the fact that the CDR record stores three
events: the "Start" time, the "Answer" time, and the "End" time. Billing time is
@@ -16,7 +16,7 @@
The fundamental assumption is that the Channel is the fundamental communication
object in asterisk, which basically provides a communication channel between two
communication ports. It makes sense to have an event system aimed at recording
-important events on channels. Each Event is attached to a channel, like ANSWER
+important events on channels. Each event is attached to a channel, like ANSWER
or HANGUP. Some events are meant to connect two or more channels, like the
BRIDGE\_START event. Some events, like BLINDTRANSFER, are initiated by one
channel, but affect two others. These events use the Peer field, like BRIDGE
@@ -27,7 +27,7 @@
a few different examples that could be used as a basis for those involved in
this effort.
-There are definite parallels between Manager events and CEL events; but there
+There are definite parallels between Manager events and CEL events, but there
are some differences. Some events that are generated by CEL are not generated
by the Manager interface (yet). CEL is optimized for databases, and Manager
events are not. The focus of CEL is billing. The Manager interface is targeted
@@ -48,6 +48,7 @@
This sequence of actions will generate the following annotated list of 42 CEL
events:
+\begin{astlisting}
\begin{verbatim}
"EV_CHAN_START","2007-05-09 12:46:16","fxs.52","152","","","","s","extension","Zap/52-1","","","DOCUMENTATION","","1178736376.3","","" ;;; 152 takes the phone off-hook
"EV_APP_START","2007-05-09 12:46:18","fxs.52","152","152","","","151","extension","Zap/52-1","Dial","Zap/51|30|TtWw","DOCUMENTATION","","1178736376.3" ;;; 152 finishes dialing 151
@@ -101,10 +102,12 @@
"EV_HANGUP","2007-05-09 12:50:13","fxs.50","150","150","","","h","extension","Zap/50-1","","","DOCUMENTATION","","1178736471.6","","" ;;; 150 hangs up
"EV_CHAN_END","2007-05-09 12:50:13","fxs.50","150","150","","","h","extension","Zap/50-1","","","DOCUMENTATION","","1178736471.6","","" ;;; 150 ends
\end{verbatim}
+\end{astlisting}
In terms of Manager events, the above Events correspond to the following 80
Manager events:
+\begin{astlisting}
\begin{verbatim}
Event: Newchannel
Privilege: call,all
@@ -759,14 +762,17 @@
Cause: 16
Cause-txt: Normal Clearing
\end{verbatim}
+\end{astlisting}
And, humorously enough, the above 80 manager events, or 42 CEL events,
correspond to the following two CDR records (at the moment!):
+\begin{astlisting}
\begin{verbatim}
""fxs.52" <152>","152","h","extension","Zap/52-1","Zap/51-1","NoOp","More Hangup message after hopping around"","2007-05-09 17:35:56","2007-05-09 17:36:20","2007-05-09 17:36:36","40","16","ANSWERED","DOCUMENTATION","","1178753756.0",""
""fxs.50" <150>","150","152","extension","Zap/50-1","Zap/51-1","NoOp","More Hangup message after hopping around"","2007-05-09 17:37:59","2007-05-09 17:38:06","2007-05-09 17:39:11","72","65","ANSWERED","DOCUMENTATION","","1178753871.3",""
\end{verbatim}
+\end{astlisting}
\section{Events \& Fields}
@@ -888,13 +894,12 @@
\section{Configuration Files}
-\section{Storage Backends}
-
-Right now, the CEL package will support CSV, Customized CSV, ODBC, PGSQL, TDS,
-Sqlite, Sqlite3, and Radius database backends. See the doc/celdriver.tex file
-for how to use these back ends.
+\begin{itemize}
+\item cel.conf
+\end{itemize}
\section{Generating Billing Information}
-** this is the Next Big Task ***
-
+*** This is the Next Big Task ***
+
+
Modified: team/group/newcdr/doc/tex/celdriver.tex
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/newcdr/doc/tex/celdriver.tex?view=diff&rev=202797&r1=202796&r2=202797
==============================================================================
--- team/group/newcdr/doc/tex/celdriver.tex (original)
+++ team/group/newcdr/doc/tex/celdriver.tex Tue Jun 23 17:27:39 2009
@@ -1,6 +1,10 @@
-Channel Event records can be stored in many different databases or even CSV text.
-
-\section{Microsoft SQL Server}
+\section{Storage Backends}
+
+Right now, the CEL package will support CSV, Customized CSV, ODBC, PGSQL, TDS,
+Sqlite3, and Radius back ends. See the doc/celdriver.tex file
+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
@@ -12,7 +16,7 @@
NOTE: Only choose one db connector.
-\subsection{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 &&
@@ -109,7 +113,7 @@
logs a connection to the database and will now record every
desired channel event at the moment it occurs.
-\subsection{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 &&
@@ -172,11 +176,11 @@
call to the database when it's complete.
-\section{MySQL}
+\subsection{MySQL}
Using MySQL for Channel Event records is supported by using ODBC and the cel\_odbc module.
-\section{PostreSQL}
+\subsection{PostreSQL}
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.
@@ -221,13 +225,13 @@
);
\end{verbatim}
-\section{SQLite 3}
+\subsection{SQLite 3}
SQLite version 3 is supported in cel\_sqlite3\_custom.
-\section{RADIUS}
-
-\subsection{What is needed}
+\subsection{RADIUS}
+
+\subsubsection{What is needed}
\begin{itemize}
\item FreeRADIUS server
@@ -264,8 +268,6 @@
\caption{Asterisk/RADIUS Integration}
\end{figure}
-\subsection{Steps to follow in order to have RADIUS support}
-
\subsubsection{Installation of the Radiusclient library}
Installation:
\begin{verbatim}
@@ -421,7 +423,7 @@
the radiusclient-ng library configuration file.
-\section{Logged Values}
+\subsubsection{Logged Values}
\begin{verbatim}
"Asterisk-Acc-Code", The account name of detail records
"Asterisk-CidName",
More information about the asterisk-commits
mailing list