Are CDRs created for virtual extensions

Vietyank · June 24, 2021, 11:31am

I have a virtual extension but don’t see any CDR records for incoming calls

david55 · June 24, 2021, 11:52am

Are the calls being answered?

Vietyank · June 24, 2021, 12:36pm

The obvious problem but if not answered, why is there no CDR?

david55 · June 24, 2021, 12:53pm

Because the default option for CDRs is to not log unanswered calls.

In raw asterisk terms, see

github.com

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


; 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 log unanswered calls that don't involve an outgoing
; party. Setting this to "yes" will make calls to extensions that don't answer
; and don't set a B side channel (such as by using the Dial application)
; receive CDR log entries. If this option is set to "no", then those log
; entries will not be created. Unanswered Calls which get offered to an
; outgoing line will always receive log entries regardless of this option, and
; that is the intended behaviour.
;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. Default

I don’t know if there is a GUI equivalent, as I’m only answering questions here that appear to relate to the underlying Asterisk system.

Vietyank · June 24, 2021, 1:26pm

Where is that file?

david55 · June 24, 2021, 1:35pm

It will be maintained by FreePBX, so you probably can’t edit it directly, but it would normally be /etc/asterisk/cdr.conf

However, this seems to suggest that FreePBX simply creates an empty one, if it doesn’t already exist:

Vietyank · June 24, 2021, 1:48pm

No such file exists. Not sure where to go from here

david55 · June 24, 2021, 2:01pm

Two possibilities:

The files aren’t in default Asterisk configuration directory (the same as the other .conf files).
It proved unnecessary to create an empty one. (Create it.)

However, both of these relate to FreePBX, rather than raw Asterisk.

Vietyank · June 25, 2021, 3:52am

I have access to asterisk from the shell This file does not exist. I grepped the string “unanswered = no” and found no file containing that string.

Any freePBX experts that have some suggestions? Can I just copy this file and call it /etc/asterisk/cdr.conf?

dicko · June 25, 2021, 4:05am

That file can be used to by asterisk to define text file based cdr logs, FreePBX no longer generates cdr csv files prefering odbc (Mysql) logs,

rasterisk -x 'cdr show status'

will show you the backends you are currently using
The currently distributed raw file defining cdr odbc reporting is

github.com

mitrefccace/asterisk/blob/master/config/cdr_adaptive_odbc.conf

; 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.
;
; The columns in the tables should match up word-for-word (case-insensitive)
; to the CDR variables set in the dialplan.  The natural advantage to this
; system is that beyond setting up the configuration file to tell you what
; tables to look at, there isn't anything more to do beyond creating the

This file has been truncated. show original

Vietyank · June 25, 2021, 4:20am

Call Detail Record (CDR) settings

Logging: Enabled
Mode: Simple
Log unanswered calls: No
Log congestion: No

Registered Backends
Adaptive ODBC

Vietyank · June 25, 2021, 4:21am

So how do I modify it to Log unanswered calls?

dicko · June 25, 2021, 4:26am

create the cdr.conf file with any non default settings or use an edited template and module load cdr_csv.so then run the cdr show status again and if you enabled csv and it shows it as a registered ‘backend’ then the logs in /var/log/aserisk/cdr-csv/ will start to be populted.

Stewart1 · June 25, 2021, 4:29am

Default is /var/log/asterisk/cdr-csv/

dicko · June 25, 2021, 4:31am

hehe, it certainly is.

Corrected

Vietyank · June 25, 2021, 4:31am

Why would I want to changed to csv and not mySQL?

dicko · June 25, 2021, 4:34am

You are not changing from anything, you can have many backends active, I can’t say whether changing that behavior affects all the backends, that will be for you to find out. It certainly affect the Master.csv file.

Vietyank · June 25, 2021, 4:41am

The Adaptive ODBC backend says unanswered calls are not logged I was hoping there was a way to modify that through the GUI

Vietyank · June 25, 2021, 5:52am

I am surprised there is no place in advanced settings to do this.

PitzKey · June 25, 2021, 7:33am

File a feature request: issues.freepbx.org

Are CDRs created for virtual extensions

Call Detail Record (CDR) settings

Registered Backends