mirror of
https://github.com/asterisk/asterisk.git
synced 2026-05-04 20:33:53 +00:00
71a8457d53
Asterisk now supports using ODBC with databases where a single schema must be selected. Previously, INSERTs would fail because they did not take into account extra fields cause by having multiple schemas. This also corrects some SQL resource leaks. (closes issue ASTERISK-17106) Patch-by: Alexander Frolkin Patch-by: Tilgnman Lesher git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@353964 65c4cc65-6c06-0410-ace0-fbb531ad65f3
66 lines
2.7 KiB
Plaintext
66 lines
2.7 KiB
Plaintext
;
|
|
; This configuration defines the connections and tables for which CDRs may
|
|
; be populated. Each context specifies a different CDR table to be used.
|
|
;
|
|
; The columns in the tables should match up word-for-word (case-insensitive)
|
|
; to the CDR 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
|
|
; CDR variables in the dialplan. For the builtin variables only, you may
|
|
; create aliases for the real column name.
|
|
;
|
|
; 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.
|
|
;
|
|
|
|
;[first]
|
|
;connection=mysql1
|
|
;table=cdr
|
|
|
|
;[second]
|
|
;connection=mysql1
|
|
;table=extracdr
|
|
|
|
;[third]
|
|
;connection=sqlserver
|
|
;table=AsteriskCDR
|
|
;schema=public ; for databases which support schemas
|
|
;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 CDR will be discarded
|
|
;filter accountcode => somename
|
|
;filter src => 123
|
|
; Negative filters are also now available
|
|
;filter src != 456
|
|
;
|
|
; 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
|
|
|
|
|
|
; On Wednesday 10 September 2008 21:11:16 Tilghman Lesher wrote:
|
|
;
|
|
; I thought that the sample cdr_adaptive_odbc.conf was rather clear, but
|
|
; apparently not. The point of this module is to allow you log whatever you
|
|
; like in terms of the CDR 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 the configuration
|
|
; file that maps the standard CDR field name (uniqueid) to whatever column
|
|
; name you like. Perhaps you'd like some extra CDR values logged that aren't
|
|
; in the standard repertoire of CDR variables (some that come to mind are
|
|
; certain values used for LCR: route, per_minute_cost, and per_minute_price).
|
|
; Simply set those CDR variables in your dialplan, i.e. Set(CDR(route)=27),
|
|
; ensure that a corresponding column exists in your table, and cdr_adaptive_odbc
|
|
; will do the rest.
|
|
|