Skip to main content

Horrid CDR's

Posted by The Godfather on Thu, 06/28/2012

It's no secret that CDR's within thirdlane leave a lot to be desired. 90 percent of our customers need more detailed CDR's so I am requesting some feedback to see what, if anything you guys are using to provide customers with a much needed solution.

Thanks in advance!


Submitted by The Godfather on Thu, 06/28/2012 Permalink

I'd also like to add that the CDR's can't even be searched through very far back. They master csv file appears to get renamed to mastercsv.1 .2 3., etc... and those become unsearchable... Am I wrong, is mine configured improperly?

Submitted by eeman on Fri, 06/29/2012 Permalink

you did it wrong, use the MySQL database for searches, the records stay as long as they exist in the db, you have to do your own manual purge every few years or so.

Submitted by The Godfather on Fri, 06/29/2012 Permalink

Eeman, Thanks for the reply on the SQL database solution. I had changed it while playing around with webcdr's and was wondering why it got so slow all the sudden :)

I did notice you avoided my first question though :) What would you recommend for that?

Submitted by eeman on Sun, 07/01/2012 Permalink

the records are all in tact, its just the data presented on the webpage that only shows some of the fields. however, my customers seem to be fine with the information theyre limited to.

Submitted by joshe on Sat, 07/14/2012 Permalink

If you are interested, we've experimented with a few custom solutions to improve the quality of CDR data. There are fixes required for things like Local/ channel abstractions, as well as visual representations of the data itself.

We use this internally for our own customers, but have looked at options to extend this to other companies as well.

As a hint, none of this is done in the webmin framework. We use a combination of adaptive CDR functionality in Asterisk 1.8, CEL, and some dialplan magic to make this stuff work a great deal better than it does out of the box, for us anyway.

Josh