diff options
Diffstat (limited to 'configs')
| -rw-r--r-- | configs/cdr_adaptive_odbc.conf.sample | 31 |
1 files changed, 13 insertions, 18 deletions
diff --git a/configs/cdr_adaptive_odbc.conf.sample b/configs/cdr_adaptive_odbc.conf.sample index 775e9abb2..f3c806e75 100644 --- a/configs/cdr_adaptive_odbc.conf.sample +++ b/configs/cdr_adaptive_odbc.conf.sample @@ -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 ; be populated. Each context specifies a different CDR table to be used. @@ -41,25 +53,8 @@ ; Negative filters are also now available ;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 ; 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. - |