diff options
author | Tilghman Lesher <tilghman@meg.abyt.es> | 2010-08-29 02:52:25 +0000 |
---|---|---|
committer | Tilghman Lesher <tilghman@meg.abyt.es> | 2010-08-29 02:52:25 +0000 |
commit | 34cce24a9c10b177d93650b6003c82d80cd9aa4d (patch) | |
tree | 658a452cd68a792545cdd30250510f42915bf0ef /configs/cel_odbc.conf.sample | |
parent | dce0822d603b0151a6d6c4fe6c83c41f3155da9d (diff) |
Merged revisions 284096 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.8
........
r284096 | tilghman | 2010-08-28 21:51:14 -0500 (Sat, 28 Aug 2010) | 3 lines
Rename CEL adaptive driver to plain driver, since there isn't another ODBC driver
(and the other CEL drivers have adaptive capabilities, anyway).
........
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@284097 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'configs/cel_odbc.conf.sample')
-rw-r--r-- | configs/cel_odbc.conf.sample | 99 |
1 files changed, 99 insertions, 0 deletions
diff --git a/configs/cel_odbc.conf.sample b/configs/cel_odbc.conf.sample new file mode 100644 index 000000000..5f21326df --- /dev/null +++ b/configs/cel_odbc.conf.sample @@ -0,0 +1,99 @@ +; +; Asterisk Channel Event Logging (CEL) - Adaptive ODBC Backend +; + +; This configuration defines the connections and tables for which CEL records +; may be populated. Each context specifies a different CEL table to be used. +; +; The columns in the tables should match up word-for-word (case-insensitive) to +; the CEL variables set in the dialplan. The natural advantage to this system +; is that beyond setting up the configuration file to tell you what tables to +; look at, there isn't anything more to do beyond creating the columns for the +; fields that you want, and populating the corresponding CEL variables in the +; dialplan. +; +; Please note that after adding columns to the database, it is necessary to +; reload this module to get the new column names and types read. +; +; Warning: if you specify two contexts with exactly the same connection and +; table names, you will get duplicate records in that table. So be careful. +; +; CEL FIELDS: +; eventtype +; CEL_CHANNEL_START = 1 +; CEL_CHANNEL_END = 2 +; CEL_HANGUP = 3 +; CEL_ANSWER = 4 +; CEL_APP_START = 5 +; CEL_APP_END = 6 +; CEL_BRIDGE_START = 7 +; CEL_BRIDGE_END = 8 +; CEL_CONF_START = 9 +; CEL_CONF_END = 10 +; CEL_PARK_START = 11 +; CEL_PARK_END = 12 +; CEL_BLINDTRANSFER = 13 +; CEL_ATTENDEDTRANSFER = 14 +; CEL_TRANSFER = 15 +; CEL_HOOKFLASH = 16 +; CEL_3WAY_START = 17 +; CEL_3WAY_END = 18 +; CEL_CONF_ENTER = 19 +; CEL_CONF_EXIT = 20 +; CEL_USER_DEFINED = 21 +; CEL_LINKEDID_END = 22 +; CEL_BRIDGE_UPDATE = 23 +; CEL_PICKUP = 24 +; CEL_FORWARD = 25 +; eventtime (timeval, includes microseconds) +; userdeftype (set only if eventtype == USER_DEFINED) +; cid_name +; cid_num +; cid_ani +; cid_rdnis +; cid_dnid +; exten +; context +; channame +; appname +; appdata +; accountcode +; peeraccount +; uniqueid +; linkedid +; amaflags (an int) +; userfield +; peer + +; The point of this module is to allow you log whatever you like in terms of the +; CEL variables. Do you want to log uniqueid? Then simply ensure that your +; table has that column. If you don't want the column, ensure that it does not +; exist in the table structure. If you'd like to call uniqueid something else +; in your table, simply provide an alias in this file that maps the standard CEL +; field name (uniqueid) to whatever column name you like. + +;[first] +;connection=mysql1 +;table=cel + +;[second] +;connection=mysql1 +;table=extracel + +;[third] +;connection=sqlserver +;table=AsteriskCEL +;usegmtime=yes ; defaults to no +;alias src => source +;alias channel => source_channel +;alias dst => dest +;alias dstchannel => dest_channel + +; Any filter specified MUST match exactly or the CE will be discarded +;filter accountcode => somename +;filter src => 123 + +; Additionally, we now support setting static values per column. Reason +; for this is to allow different sections to specify different values for +; a certain named column, presumably separated by filters. +;static "Some Special Value" => identifier_code |