CDR doesn't work afther upgrade

FreePBX Installation / Upgrade
1

I upgraded the asterisk from 1.2 to 1.4
freepbx is now 2.3.1.3

afhter the upgrade i don’t get any cdr info.

the module cdr_addin_mysql.so is there, but when i do show modules it doesn’t show up.
when i try to manual load the cdr_addin_mysql.so i don’t get any error, but when i then do a show modules it doesn’t show it.

but it shows
cdr_manager
cdr_custom
cdr_csv

2

What version of asterisk did you upgrade too? I had CDR working right up to 1.4.17 I just upgraded to
1.4.18 and CDR stopped too. I did a quick check of the Full log file and noticed a number of CDR Reset
entries. Haven’t looked too deeply into this to see if the CDR Reset was being called before the upgrade. Anyway, why not

Trace through your logfile and see where in the dialplan that CDR Reset is being called.

Post your results back here if you can.

Thanks…

3

Same problem. A solution for this would be great!

4

same problem here as well…

5

This was the fix (on CentOS 5.1):

Then recompile asterisk-addons-1.4-current and restart asterisk. Before doing this, configuring asterisk-addons looked like this:

# ./configure | grep sql
checking for mysql_config... /usr/bin/mysql_config
checking for mysql_init in -lmysqlclient... no

But afterward:

# ./configure | grep sql
checking for mysql_config... /usr/bin/mysql_config
[b]checking for mysql_init in -lmysqlclient... yes[/b]

Finally, ‘mysql’ shows up in asterisk CLI:

maryland*CLI> cdr status
CDR logging: enabled
CDR mode: simple
CDR output unanswered calls: yes
CDR registered backend: cdr-custom
CDR registered backend: csv
CDR registered backend: cdr_manager
[b]CDR registered backend: mysql[/b]
6

Then you need to enable the load=>cdr_addon_mysql.so to /etc/asterisk/modules.conf

restart asterisk

/etc/init.d/asterisk stop
/etc/init.d/asterisk start

The information here was helpful, but this is what was required to fix it.

Thanks to all.