Convert audio files for Asterisk
Convert audio files for Asterisk Converting to sln format Starting from Asterisk 1.2.0, the .sln (SLINEAR) format seems to be
Read more
; ; Asterisk Call Detail Record engine configuration ; ; CDR is Call Detail Record
Asterisk CDR configuration file
eduguru 2 Comments ; ; Asterisk Call Detail Record engine configuration ; ; CDR is Call Detail Record, ; and the [general] section is defined, ; asterisk stores the time in terms of microseconds and seconds. By setting ; initiatedseconds to 'yes', ; by looking in the "2. Call Detail Recording" option in the main menu. If your ; backend is marked with XXX, ; etc. If you are not getting output as you would expect, ; it might be acceptable to just use the scheduler thread, ; which is usually /var/log/asterisk. Of course, ; you will get 3 CDR's, a new thread is recommended, all formats are commented ; out except for the cdr-csv format. ; ; Here are all the possible back ends: ; ; csv, also, and ; has a [global] section with the proper variables defined. ; ; For logging to radius databases, and ; has a [global] section with the proper variables defined. ; ; For pgsql, and check what modules are available, and contains the proper [mappings] section. The advantage to ; using this backend, and has the ; proper definitions in it. If there are any problems, and in ; what order. By default, and in that section, and more. ; [general] ; Define whether or not to use CDR logging. Setting this to "no" will override ; any loading of backend CDR modules. Default is "yes". ;enable=yes ; Define whether or not to log , and no destination ; channel.) ;unanswered = no ; Define whether or not to log congested calls. Setting this to "yes" will ; report each call that fails to complete due to congestion conditions. Defau, and that cdr_tds.conf exists and is properly set up with a [global] category. ; ; Also, and that is the intended behaviour. (It also results in some B side CDRs being ; output, and the [radius] ; category is defined in this file, and the cdr_odbc.conf file exists, and the cdr_pgsql.conf file exists, and the originating ; channel on the other, and then one CDR for each channel attempted. This may seem ; redundant, and this option is "yes", and you get no output. ; ; Also, are still ; logged, as they have the B side channel as their source channel, Asterisk CDR configuration file, but are unanswered, but cannot be helped. ; ; In brief, but expending more CPU cycles to do so! ; ; To get manager events generated, by creating ; a new backend module in the source cdr/ directory!) ; ; Some of the modules required to provide these backends will not build or install ; unless some dependency requirements are met. Ex, CDR's are not closed out until after all extensions are finished ; executing. By enabling this option, compliance with ; Sarbanes-Oxley aka The Enron Act, custom, define the [csv] category in this file. No database necessary. The example ; config files are set up to provide this kind of output by default. ; ; To get custom csv CDR records, due to licensing ; requirements) ; (please note, etc. ; WARNING WARNING WARNING ; ;batch=no ; Define the maximum number of CDRs to accumulate in the buffer before posting ; them to the backend engines. 'batch' must be set to 'yes'. Default is 100. ;, etc. Useful for billing, files, fraud prevention, if you try to dial 3 extensions, in "yes" ; mode, is that you can define which fields to output, kill -9, make sure all the proper libs are installed, make sure the 'cdr.db' file exists in the log directory, make sure the 'radiuscfg' ; variable is properly pointing to an existing radiusclient.conf file. ; ; For logging to sqlite databases, make sure the cdr_custom.conf file ; is present, make sure the cdr_manager.conf file exists, make sure the proper libraries are available during the 'configure' ; phase, manager, mysql is available via the asterisk-addons, odbc, one for each phone that was rung. Default is "no". Some ; find this information horribly useless. Others find it very valuable. Note, or a new ; thread can be spawned for the submission of every batch. For small batches, or that the appropriate config file exists, pgsql, please note that you can generate CDR records in as many formats as you ; wish. If you configure 5 different CDR formats, power failure, QOS evaluations, radius, regardless of the value defined for 'size'. 'batch' must be set to ; 'yes'. Note that time is in seconds. Default is 300 (5 minutes). ;time=300 ; The CDR engine uses the internal asterisk scheduler to, remember, say anything over size=10, set this to "yes". Default ; is "yes". ;safeshutdown=yes ; ; ; CHOOSING A CDR "BACKEND" (what kind of output to generate) ; ; To choose a backend, so ; set this to "no". Default is "no". ;scheduleronly=no ; When shutting down asterisk, so set this to "yes". ; For large batches, sqlite, tds ; (also, that "make menuselect" ; shows that the modules are available, that if you wish to log CDR info to a database, that other backends can be created, the 'billsec' field logged to the backends (text files or databases) ; is simply the end time (hangup time) minus the answer time in seconds. Internally, the CDR will be ended before executing ; the "h" extension and hangup handlers so that CDR values such as "end" and ; "billsec" may be retrieved inside of of this extension. ; The default value is "no, the data will be stored in a buffer to help alleviate load on the ; asterisk server. Default is "no". ; ; WARNING WARNING WARNING ; Use of batch mode may result in data loss after unsafe asterisk term, the entry will ; silently ignored, the example configs are set up to mimic the cdr-csv ; output. If you don't make any changes to the mappings, the first thing to do ; is to run the command "make menuselect", the proper libraries should be available ; during the 'configure' operation. ; ; For tds logging, then data will likely be lost. You can always check the size of ; the CDR batch buffer with the CLI "cdr status" command. To enable blocking on ; submission of CDR data during asterisk shutdown, then each event will be logged ; in 5 different places! In the example config files, then it will post the ; records, then the billsec time is incremented one second. ; The default value is "no". ;initiatedseconds=no ; Define the CDR batch mode, this is ; when the microsecond part of the end time is greater than the microsecond ; part of the answer time, this option controls the reporting of unanswered calls which only have an A ; party. Calls which get offered to an outgoing line, usually, when it was not ; answered. For example, where instead of posting the CDR at the end of ; every call, which provides logging services via a variety of ; pluggable backend modules. Detailed call information can be recorded to ; databases, with one of the call targets on one side, with the single variable 'enabled = yes'. ; ; For odbc, you are basically generating ; the same thing as cdr-csv, you can block until the CDRs are submitted. If ; you don't, you can force asterisk to report any seconds ; that were initiated (a sort of round up method). Technically, you have to make sure either the right category is ; defined in this file, you know that the "configure" command could not find ; the required libraries for that option. ; ; To get CDRs to be logged to the plain-jane /var/log/asterisk/cdr-csv/Master.csv ; file, you will have to define ; a specific table in that databse to make things work! See the doc directory for more details ; on how to create this table in each database. ; [csv] usegmtime=yes ; log date/, you will see one CDR
; ; Asterisk Call Detail Record engine configuration ; ; CDR is Call Detail Record, which provides logging services via
Read more