Datasets:
Squidnutz
/
extractedtest

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
0
152
cdr_adaptive_odbc.conf file.
Call Detail Records
|
359
Table 21-4. cdr_adaptive_odbc.conf table configuration options
Option
connection pgsql1
Value/example
Notes
The database connection to be used. This is a reference to the configured connection in
res_odbc.conf. This field is required.
table
usegmtime
asterisk_cdr The table name. This field is required.
no
Indicates whether to log timestamps using GMT instead of local time. The default value
for this option is no.
In addition to the key/value pair fields that are shown in the previous table, cdr_adap‐
tive_odbc.conf allows for a few other configuration items. The first is a column alias.
Normally, CDR variables are logged to columns of the same name. An alias allows
the variable name to be mapped to a column with a different name. The syntax is:
alias CDR variable => column name
Here is an example column mapping using the alias option:
alias src => source
It is also possible to specify a content filter. This allows you to specify criteria that
must match for records to be inserted into the table. The syntax is:
filter CDR variable => content
Here is an example content filter:
filter accountcode => 123
Finally, cdr_adaptive_odbc.conf allows static content for a column to be defined. This
can be useful when combined with a set of filters. This static content can help dif‐
ferentiate records that were inserted into the same table by different configuration
sections. The syntax for static content is:
static "Static Content Goes Here" => column name
Here is an example of specifying static content to be inserted with CDRs:
static "My Content" => my_identifier
cdr_csv
The cdr_csv module is a very simple CDR backend that logs CDRs into a CSV
(comma-separated values) file. The file is /var/log/asterisk/cdr-csv/Master.csv. As long
as CDR logging is enabled in cdr.conf and this module has been loaded, CDRs will be
logged to the Master.csv file. We recommend that regardless of any other CDR back‐
end you choose to configure, you leave this configured as well, as it will serve as an
excellent backup should you lose other CDR data due to network or related issues.
360
|
Chapter 21: System Monitoring and Logging
While no options are required to get this module working, there are some options
that customize its behavior. These options, listed in Table 21-5, are placed in the
[csv] section of cdr.conf.
Table 21-5. cdr.conf [csv] section options
Option
usegmtime
Value/example Notes
no
loguniqueid
no
loguserfield no
accountlogs
yes
Log timestamps using GMT instead of local time. The default is no.
Log the uniqueid CDR variable. The default is no.
Log the userfield CDR variable. The default is no.