CDR is blank [resolved]

No information is being recorded to the CDR.

I’ve looked at the table directly with phpmyadmin and it’s empty.
The reports module shows no information
ARI shows nothing
Calls that should be recorded dont show anywhere.
I’m baffled.

typing “cdr status” in the CLI gives:
CDR logging: enabled
CDR mode: simple

So that seems happy, I’ve been digging through this for a while and as this is a from source install I think I’ve missed an important part of the big picture somewhere along the way.

Asterisk 1.4.7.1
Freepbx 2.3.0beta 1.9 (framework 2.3.0beta1.6)
Debian 4.0

do you have the asterisk addons package installed? - you may want to try reinstalling that.

at the asterisk cli type cdr status

should look like this
asterisk1*CLI> cdr status
CDR logging enabled
CDR mode simple
CDR registered backend mysql
CDR registered backend csv
CDR registered backend cdr_manager

if it says csv twice, you need to reintall the addons.

here’s the output of ./configure after a make clean in the asterisk-addons directory:

[code:1]
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking target system type… i686-pc-linux-gnu
checking for uname… /bin/uname
checking for gcc… gcc
checking for C compiler default output file name… a.out
checking whether the C compiler works… yes
checking whether we are cross compiling… no
checking for suffix of executables…
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ISO C89… none needed
checking for g++… g++
checking whether we are using the GNU C++ compiler… yes
checking whether g++ accepts -g… yes
checking for a BSD-compatible install… /usr/bin/install -c
checking whether ln -s works… yes
checking for GNU make… make
checking for grep… /bin/grep
checking for basename… /usr/bin/basename
checking for dirname… /usr/bin/dirname
checking for sh… /bin/sh
checking for ln… /bin/ln
checking how to run the C preprocessor… gcc -E
checking for grep that handles long lines and -e… (cached) /bin/grep
checking for egrep… /bin/grep -E
checking for ANSI C header files… yes
checking for sys/types.h… yes
checking for sys/stat.h… yes
checking for stdlib.h… yes
checking for string.h… yes
checking for memory.h… yes
checking for strings.h… yes
checking for inttypes.h… yes
checking for stdint.h… yes
checking for unistd.h… yes
checking for initscr in -lcurses… yes
checking curses.h usability… yes
checking curses.h presence… yes
checking for curses.h… yes
checking for initscr in -lncurses… yes
checking for curses.h… (cached) yes
checking for mysql_config… no <========================
checking for asterisk.h… yes
configure: creating ./config.status
config.status: creating build_tools/menuselect-deps
config.status: creating makeopts

           .$$$$$$$$$$$$$$$=..
        .$7$7..          .7$$7:.
      .$$:.                 ,$7.7
    .$7.     7$$$$           .$$77
 ..$$.       $$$$$            .$$$7
..7$   .?.   $$$$$   .?.       7$$$.

$.$. .$$$7. $$$$7 .7$$$. .$$$.
.777. .$$$$$$77$$$77$$$$$7. $$$,
$$$~ .7$$$$$$$$$$$$$7. .$$$.
.$$7 .7$$$$$$$7: ?$$$.
$$$ ?7$$$$$$$$$$I .$$$7
$$$ .7$$$$$$$$$$$$$$$$ :$$$.
$$$ $$$$$$7$$$$$$$$$$$$ .$$$.
$$$ $$$ 7$$$7 .$$$ .$$$.
$$$$ $$$$7 .$$$.
7$$$7 7$$$$ 7$$$
$$$$$ $$$
$$$$7. $$ ™
$$$$$$$. .7$$$$$$ $$
$$$$$$$$$$$$7$$$$$$$$$.$$$$$$
$$$$$$$$$$$$$$$$.

configure: Package configured for:
configure: OS type : Linux
configure: Host CPU : i686
[/code:1]

Bold etc dont work in code mode, so I’ve put an arrow by the troubling line. So it thinks I dont have a mysql client installed huh? Ok then, aptitude install libmysqlclient-dev and try again, this time the same sectin came back as

[code:1]
checking for mysql_config… /usr/bin/mysql_config
checking for mysql_init in -lmysqlclient… yes
[/code:1]

So that looks better.

After recompiling addons, installing it and restarting asterisk, the output of cdr status now looks like this:

[code:1]
asterisk*CLI> cdr status
CDR logging: enabled
CDR mode: simple
CDR registered backend: mysql
[/code:1]

Time for some tests!

Looks like a fix!

Considering that line in the configure is so easy to miss, this sure causes a problem or two )

Call recordings, call monitors and call data logging is now working fine.
Thanks for the pointer totalimpact