Skip to main content

CDR BUG: MTE 7.1.1.5 PBX not logging CDR to mysql

Posted by telair on Tue, 04/01/2014

Hello

The installation is on an MTE 7.1.1.5
Installed with text configuration files (not mysql storage for asterisk)
Installed with cdr+mysql storage for cdr + queue logs

System works well. Found a bug that the system does not log any cdr records at all in mysql.
When in Cluster Management -> System Settings -> PBX Logs
all settings are correct, and when I press test connection i see: Success

When I view the contents of the mysql database of pbxlogs there is no data in the table 'cdr'.
However there is information in other tables logging correctly such as: 'call_status'

So I know the mysql connection is working.

Although I can view call logs through the CDR via the /var/log/asterisk/cdr-csv
The option to click and view call detail records from the portal does not work. The response is "No items to show".

How can I correct this without a complete format and reload?

Thank you,


Submitted by summitgroup on Sat, 04/05/2014 Permalink

Hi,

I had this issue some time ago and the response from support was;

"This issue will not happen again, for some reason one of the config parameters was out of the "stanza" scope."

I'm really not too sure what they did to correct the issue but I hope this may point you in the right direction.

Cheers,

Greg

Submitted by telair on Sun, 04/06/2014 Permalink

Thanks Greg

Was there something done to your issue to update the config file?

Thank you

Submitted by summitgroup on Thu, 10/16/2014 Permalink

Hi Telair,

I managed to get this going recently when I forklifted to a fresh server.

It was incorrect module was loaded. It was trying to use cdr_adaptive rather than cdr_mysql from memory.

Here is a dump from asterisk;

sip*CLI> cdr show status

Call Detail Record (CDR) settings
----------------------------------
Logging: Enabled
Mode: Simple
Log unanswered calls: No

* Registered Backends
-------------------
mysql
csv
cdr-custom

Submitted by eeman on Mon, 10/27/2014 Permalink

its supposed to use cdr_adaptive... your problem was a bug in the .conf file that was fixed in later releases. without cdr_adaptive it wont execute a stored procedure at the end of the call. The problem is that this line was placed in the wrong location.. it needs to appear after the [cdr1] not before..

callafterinsert => cdr_update_nested_calls