Cdr_csv and cdr_custom

ctrl1122 · May 10, 2022, 8:29pm

Hello,

Where can I find the default mapping for cdr_csv reporting(which columns/fields are selected to generate the Master.csv)? Or would anyone happen to know the names of the columns that are selected from asteriskcdrdb to generate the Master.csv under /var/log/asterisk/cdr-csv? I just migrated from vanilla asterisk 13 to freePBX 16. On my vanilla asterisk system there is a script that generates a report using the CDR stats logged to Master.csv. It looks like the schema on the new system has changed and does not log stats in the same way to Master.csv.

On my freepbx system, I’m unable to generate a report with the “default” mapping, I had to create cdr_custom.conf and add the mapping there to get a Master.csv created. When I check the modules registered to the cdr backend I see cdr-custom but not cdr_csv. I can see that the cdr_csv module is running. If I knew what the column IDs on the asterisk 13 system I could recreate the report but from what I can tell the machine only has sqlite3 installed and doesn’t list and DBs or tables that I could look at to compare.

david55 · May 10, 2022, 8:43pm

I don’t understand why there should have been a change, but cdr-csv data never goes through a database, and has a fixed format, as documented at

github.com

asterisk/asterisk/blob/master/cdr/cdr_csv.c#L70

      
        
            static const char config[] = "cdr.conf";
            static char file_csv_master[PATH_MAX];
            
            
/* #define CSV_LOGUNIQUEID 1 */
            /* #define CSV_LOGUSERFIELD 1 */
            
            
/*----------------------------------------------------
              The values are as follows:
            
            

            
  "accountcode", 	accountcode is the account name of detail records, Master.csv contains all records *
              			Detail records are configured on a channel basis, IAX and SIP are determined by user *
            			DAHDI is determined by channel in dahdi.conf
              "source",
              "destination",
              "destination context",
              "callerid",
              "channel",
              "destination channel",	(if applicable)
              "last application",	Last application run on the channel
              "last app argument",	argument to the last channel

The code that constructs the record, and in which you can see the field names from the cdr data structure starts at

github.com

asterisk/asterisk/blob/master/cdr/cdr_csv.c#L216

      
        
            	ast_strftime(tmp, sizeof(tmp), DATE_FORMAT, &tm);
            
            
	return append_string(buf, tmp, bufsize);
            }
            
            
static int build_csv_record(char *buf, size_t bufsize, struct ast_cdr *cdr)
            {
            
            
	buf[0] = '\0';
            	/* Account code */
            	append_string(buf, cdr->accountcode, bufsize);
            	/* Source */
            	append_string(buf, cdr->src, bufsize);
            	/* Destination */
            	append_string(buf, cdr->dst, bufsize);
            	/* Destination context */
            	append_string(buf, cdr->dcontext, bufsize);
            	/* Caller*ID */
            	append_string(buf, cdr->clid, bufsize);
            	/* Channel */
            	append_string(buf, cdr->channel, bufsize);

As you can see at, for example,

github.com

asterisk/asterisk/blob/master/cdr/cdr_csv.c#L248

      
        
            	append_date(buf, cdr->end, bufsize);
            	/* Duration */
            	append_int(buf, cdr->duration, bufsize);
            	/* Billable seconds */
            	append_int(buf, cdr->billsec, bufsize);
            	/* Disposition */
            	append_string(buf, ast_cdr_disp2str(cdr->disposition), bufsize);
            	/* AMA Flags */
            	append_string(buf, ast_channel_amaflags2string(cdr->amaflags), bufsize);
            	/* Unique ID */
            	if (loguniqueid)
            		append_string(buf, cdr->uniqueid, bufsize);
            	/* append the user field */
            	if(loguserfield)
            		append_string(buf, cdr->userfield, bufsize);
            	if (newcdrcolumns) {
            		append_string(buf, cdr->peeraccount, bufsize);
            		append_string(buf, cdr->linkedid, bufsize);
            		append_int(buf, cdr->sequence, bufsize);
            	}
            	/* If we hit the end of our buffer, log an error */

some fields are optional. These are controlled by the obvious options in the [csv] section of cdr.conf (FreePBX may well require you to actually use a custom file, included from this.

dicko · May 10, 2022, 9:27pm

Start with good old

github.com

asterisk/asterisk/blob/master/configs/samples/cdr.conf.sample

;
; Asterisk Call Detail Record engine configuration
;
; CDR is Call Detail Record, which provides logging services via a variety of
; pluggable backend modules.  Detailed call information can be recorded to
; databases, files, etc.  Useful for billing, fraud prevention, compliance with
; Sarbanes-Oxley aka The Enron Act, QOS evaluations, 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 use CDR logging on new channels by default.
; Setting this to "no" will disable CDR on channels unless it is explicitly
; enabled. Default is "yes".
;channeldefaultenabled=yes

This file has been truncated. show original

There can be several cdr ‘backends’ , but mostly FreePBXers rely on the built in ‘Adaptive ODBC’

A ‘goldie but oldie’ showing the default format of Master.csv

\Asterisk call data records in comma-separated text files

but if you want a ‘customize’ csv also, then you will need a /etc/asterisk/cdr.conf which ‘includes’ something like:-

asterisk/cdr_custom.conf at master · asterisk/asterisk · GitHub, take it from there.

ctrl1122 · May 11, 2022, 8:27pm

Found the root cause of the report breaking. Since we’re using PJSIP on the new freePBX system, channel and dstchannel are logged as PJSIP/XXXX instead of SIP/XXXX which was throwing off the anticipated string length for out scripted report generator. A full reboot fixed the default logging to /cdr-csv/Master.csv, and the mapping is in fact the same between both old and new systems. Thanks @david55 and @dicko for the information, I learned quite a bit and it helped narrow down the issue.

system · May 18, 2022, 8:27pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.