[OpenSIPS-Users] CDRTool Patch

[Adrian Georgescu]

It is not one table, is a new table auto created each calendar month. So you do not need to purge anything, just move the old files away.

InnoDB is too slow for the purpose of storing CDRs and you cannot move the files away on a monthly basis like you can with MyISAM format.

Adrian


On Jul 4, 2012, at 3:02 AM, Andrew Mason wrote:

> Hi All, 
> Apologies if this is the incorrect mailing list to post this the following 
> page suggests this list for keeping the page up to date.
> http://cdrtool.ag-projects.com/projects/cdrtool/wiki/Installation_Guide
> 
> I have been trying to get my head around CDR tool and came across the 
> following in /var/www/CDRTool/setup/radius/OpenSIPS/radius_accounting.proc (on 
> Debian)
> 
> 
> "Currently, call detail records generated by the OpenSIPS SIP Proxy are stored 
> into a central radius.radacct table. The radacct table grows and must be 
> manually purged, the purge operation locks the table for writing, which is 
> blocking the application that performs the queries, and this situation is 
> unacceptable."
> 
> I was wondering if this is still required if you were to use InnoDB/XtraDB 
> storage engines in MySQL/MariaDB ? Since innodb performs row level locking 
> does this remove the need to use stored procedures to purge the accounting 
> table ? If so does this mean I no longer need to recompile FreeRadius?
> 
> Many thanks
> Andrew
> 
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>