Call Event Logging always show "Search returned 0 calls"

Hello,

Current Version 10.13.66-6
FreePBX 13.0.19
Current Asterisk Version: 13.5.0

“Reports - Call Event Logging” always show “Search returned 0 calls”.

This module not work?

Wondering the same thing
CEL module 13.0.14

we are having the same problem

I’m running FreePBX 13.0.54 patched and up to date. After recent updates mid January 2016 I have noticed that the Call Event Logging Search is no longer working as well

PBX Firmware: 10.13.66-13
Current Asterisk Version: 13.9.1
FreePBX 13.0.152

“Call Event Logging” still does not work!
Any comments from developers?

If you all want this issue to be fixed please comment on

http://issues.freepbx.org/browse/FREEPBX-11623

I just reopened it, hopefully it will get some attention now.

Hi!

I had the same problem but in my case it was simply a crashed CEL table…

To fix a crashed table you need to issue something like:

mysql
use asteriscdrdb;
repair table cel;
quit;

Good luck and have a nice day!

Nick

Thanks Marbled, just tried that, but unfortunately the issue still persists.

Hi Marcelo!

If you try to do a

select * from cel

or if it has too much data

select count(*) from cel

Does it have anything in it?

Good luck and have a nice day!

Nick

It has 1.4 million rows, including rows with dates from seconds ago. It seems the logging part is being done correctly, I am guessing it to be a FreePBX problem.

Ok, I found a workaround.

On your mysql configuration (/etc/my.cnf if you use the FreePBX distro), add the line below under [mysqld] section:

max_allowed_packet=16M

Now run “/etc/init.d/mysql restart” and try again. Make sure you select some start and end dates before you click search, FreePBX there is not very smart and if it has to handle too many entries the search will crash because it will timeout (execution over 30 seconds). But at least now it works for me.

1 Like

Thank you so much for posting this workaroud, resolved the problem for me!

I am glad it helped you!

For everyone affected by this bug (the need for the workaround is due to a bug in FreePBX), please help voting for this issue in the issue tracker.

http://issues.freepbx.org/browse/FREEPBX-11623