mirror of
https://github.com/asterisk/asterisk.git
synced 2025-11-15 22:38:08 +00:00
523c95e146
Multiple revisions 350555,350571 ........ r350555 | rmudgett | 2012-01-13 11:12:51 -0600 (Fri, 13 Jan 2012) | 12 lines Add missing CEL logging fields to various CEL backends. * Add missing eventextra to cel_psql.c and cel_odbc.c. * Add missing PeerAccount and EventExtra to cel_manager.c. * Add missing userdeftype support for cel_custom.conf.sample and cel_sqlite3_custom.conf.sample. (closes issue ASTERISK-17190) Reported by: Bryant Zimmerman ........ r350571 | rmudgett | 2012-01-13 11:23:57 -0600 (Fri, 13 Jan 2012) | 8 lines Use compatible names for event extra data for various CEL backends. * Change eventextra to extra in cel_psql.c and cel_odbc.c. * Change EventExtra to Extra in cel_manager.c. (issue ASTERISK-17190) ........ Merged revisions 350555,350571 from http://svn.asterisk.org/svn/asterisk/branches/1.8 ........ Merged revisions 350585 from http://svn.asterisk.org/svn/asterisk/branches/10 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@350605 65c4cc65-6c06-0410-ace0-fbb531ad65f3
101 lines
2.9 KiB
Plaintext
101 lines
2.9 KiB
Plaintext
;
|
|
; 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
|
|
; extra
|
|
|
|
; 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
|