cdr 2.10 just showing jibbrish and no records

Please ensure you have framework 2.10.0beta3.3 installed on your system, as we added some migration for the new cdr module in 2.10.0beta3.2. This migration resolved the issue with data not showing correctly in the new cdr module.

yup have all the latest modules installed

i dont if this will help but this is the output of freepbx log
http://pastebin.com/uV6JfQUX[[BR]]
any other ides how to debug this?

http://pastebin.com/uV6JfQUX

I have experienced a similar problem with my CDR Reports ever since updating to the 2.10 betas. I have the latest of everything installed, but I get garbage in the data table below the search criteria box when I visit the CDR Reports page. I just looked at the database directly, and afaik all the normally expected data is still being correctly acquired by asterisk.

Can you run the following for me from the cli and paste the output.

amportal a m use asteriskcdrdb; describe cdr;

This should be more readable, sorry about the previous post.

Can you run the following for me from the cli and paste the output.

amportal a m
use asteriskcdrdb;
describe cdr;

Please wait...

Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 3222 Server version: 5.0.77 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> use asteriskcdrdb; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A

Database changed mysql> describe cdr; +-------------+--------------+------+-----+---------------------+-------+ | Field | Type | Null | Key | Default | Extra | +-------------+--------------+------+-----+---------------------+-------+ | calldate | datetime | NO | | 0000-00-00 00:00:00 | | | clid | varchar(80) | NO | | | | | src | varchar(80) | NO | | | | | dst | varchar(80) | NO | | | | | dcontext | varchar(80) | NO | | | | | channel | varchar(80) | NO | | | | | dstchannel | varchar(80) | NO | | | | | lastapp | varchar(80) | NO | | | | | lastdata | varchar(80) | NO | | | | | duration | int(11) | NO | | 0 | | | billsec | int(11) | NO | | 0 | | | disposition | varchar(45) | NO | | | | | amaflags | int(11) | NO | | 0 | | | accountcode | varchar(20) | NO | | | | | uniqueid | varchar(32) | NO | | | | | userfield | varchar(255) | NO | | | | | did | varchar(20) | NO | | | | +-------------+--------------+------+-----+---------------------+-------+ 17 rows in set (0.00 sec)

mysql>

Database changed

mysql> describe cdr;

+-------------+--------------+------+-----+---------------------+-------+

| Field | Type | Null | Key | Default | Extra |

+-------------+--------------+------+-----+---------------------+-------+

| calldate | datetime | NO | | 0000-00-00 00:00:00 | |

| clid | varchar(80) | NO | | | |

| src | varchar(80) | NO | | | |

| dst | varchar(80) | NO | | | |

| dcontext | varchar(80) | NO | | | |

| channel | varchar(80) | NO | | | |

| dstchannel | varchar(80) | NO | | | |

| lastapp | varchar(80) | NO | | | |

| lastdata | varchar(80) | NO | | | |

| duration | int(11) | NO | | 0 | |

| billsec | int(11) | NO | | 0 | |

| disposition | varchar(45) | NO | | | |

| amaflags | int(11) | NO | | 0 | |

| accountcode | varchar(20) | NO | | | |

| uniqueid | varchar(32) | NO | | | |

| userfield | varchar(255) | NO | | | |

| did | varchar(20) | NO | | | |

+-------------+--------------+------+-----+---------------------+-------+

17 rows in set (0.00 sec)

all this crazy wiki formatting

Can you try running the following for me:

amportal a m

use asteriskcdrdb;

ALTER TABLE cdr ADD recordingfile VARCHAR ( 255 ) NOT NULL default;

If that works, please let me know and we will need to dig into why the framework migration for 2.10.0beta3 isn't being run.

(In [13204]) re #5500 - add recordingfile field to cdr table in the cdr module as well

mysql> describe cdr;
+-------------+--------------+------+-----+---------------------+-------+
| Field       | Type         | Null | Key | Default             | Extra |
+-------------+--------------+------+-----+---------------------+-------+
| calldate    | datetime     | NO   | MUL | 0000-00-00 00:00:00 |       |
| clid        | varchar(80)  | NO   |     |                     |       |
| src         | varchar(80)  | NO   |     |                     |       |
| dst         | varchar(80)  | NO   | MUL |                     |       |
| dcontext    | varchar(80)  | NO   |     |                     |       |
| channel     | varchar(80)  | NO   |     |                     |       |
| dstchannel  | varchar(80)  | NO   |     |                     |       |
| lastapp     | varchar(80)  | NO   |     |                     |       |
| lastdata    | varchar(80)  | NO   |     |                     |       |
| duration    | int(11)      | NO   |     | 0                   |       |
| billsec     | int(11)      | NO   |     | 0                   |       |
| disposition | varchar(45)  | NO   |     |                     |       |
| amaflags    | int(11)      | NO   |     | 0                   |       |
| accountcode | varchar(20)  | NO   | MUL |                     |       |
| uniqueid    | varchar(32)  | NO   |     |                     |       |
| userfield   | varchar(255) | NO   |     |                     |       |
+-------------+--------------+------+-----+---------------------+-------+
16 rows in set (0.60 sec)

Looking at the data above, I added a couple of fields, but I still see the same gibberish when I run CDR Reports. Here's what I did:

mysql> ALTER TABLE cdr ADD did VARCHAR(20) NOT NULL default '';
Query OK, 86774 rows affected (18.57 sec)
Records: 86774  Duplicates: 0  Warnings: 0

mysql> ALTER TABLE cdr ADD recordingfile VARCHAR ( 255 ) NOT NULL default '';
Query OK, 86774 rows affected (8.28 sec)
Records: 86774  Duplicates: 0  Warnings: 0

mysql> describe cdr;
+---------------+--------------+------+-----+---------------------+-------+
| Field         | Type         | Null | Key | Default             | Extra |
+---------------+--------------+------+-----+---------------------+-------+
| calldate      | datetime     | NO   | MUL | 0000-00-00 00:00:00 |       |
| clid          | varchar(80)  | NO   |     |                     |       |
| src           | varchar(80)  | NO   |     |                     |       |
| dst           | varchar(80)  | NO   | MUL |                     |       |
| dcontext      | varchar(80)  | NO   |     |                     |       |
| channel       | varchar(80)  | NO   |     |                     |       |
| dstchannel    | varchar(80)  | NO   |     |                     |       |
| lastapp       | varchar(80)  | NO   |     |                     |       |
| lastdata      | varchar(80)  | NO   |     |                     |       |
| duration      | int(11)      | NO   |     | 0                   |       |
| billsec       | int(11)      | NO   |     | 0                   |       |
| disposition   | varchar(45)  | NO   |     |                     |       |
| amaflags      | int(11)      | NO   |     | 0                   |       |
| accountcode   | varchar(20)  | NO   | MUL |                     |       |
| uniqueid      | varchar(32)  | NO   |     |                     |       |
| userfield     | varchar(255) | NO   |     |                     |       |
| did           | varchar(20)  | NO   |     |                     |       |
| recordingfile | varchar(255) | NO   |     |                     |       |
+---------------+--------------+------+-----+---------------------+-------+
18 rows in set (0.05 sec)

OK, I think I located the problem that was causing this symptom. Although it is correct that the migration wasn't running, I suspect the real problem has to do with two references to "CDRTABLENAME" in the module code. One is located in "install.php" and the other in "page.cdr.php" in the version I just downloaded.

When I altered both of those references to use "CDRDBTABLENAME" instead of "CDRTABLENAME" my CDR reports began working correctly. In my /etc/amportal.conf there is a CDRDBTABLENAME defined, but no CDRTABLENAME.

I hope this helps.

ok it worked for me but the statment you gave gives me a error

MySQL version 5.0.77

ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1

(In [13206]) closes #5500 - use the correct array key, thanks dzone