kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-11-20 08:40:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Set snarkiness = 0 in cdr_adaptive_odbc.conf.sample

Browse Source 
........

Merged revisions 358438 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........

Merged revisions 358441 from http://svn.asterisk.org/svn/asterisk/branches/10


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358444 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Terry Wilson
2012-03-07 15:19:05 +00:00
parent 8b3704fbde
commit deded253b3
1 changed files with 13 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
configs/cdr_adaptive_odbc.conf.sample
View File

@@ -1,3 +1,15 @@
; 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.
; ;
; This configuration defines the connections and tables for which CDRs may ; This configuration defines the connections and tables for which CDRs may
; be populated. Each context specifies a different CDR table to be used. ; be populated. Each context specifies a different CDR table to be used.
@@ -41,25 +53,8 @@
; Negative filters are also now available ; Negative filters are also now available
;filter src != 456 ;filter src != 456
; ;
; Additionally, we now support setting static values per column. Reason ; Additionally, we now support setting static values per column. The reason
; for this is to allow different sections to specify different values for ; for this is to allow different sections to specify different values for
; a certain named column, presumably separated by filters. ; a certain named column, presumably separated by filters.
;static "Some Special Value" => identifier_code ;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.