Hi Robert


A while back we had similar considerations regarding CDR. What we ended up with, was to use the JSON CDR module for writing the records to disk. Then we used an custom tool[1] to upload the files to Google Cloud, where they may be indexed further.
The main idea was to store as much data as possible, as it may come in handy later. Also, the database module seemed to lack some of the information that we needed (eg. custom variables).
This worked very well for us, as we did not know from day 1 what information could be useful, and storing everything solved exactly that.

Have fun!
/Kim

[1] https://github.com/Bitstackers/openreception/tree/master/tools/cdrctl

On 2017-07-17 17:19, robert mundkowsky wrote:

What are the best practice for writing Call Detail Records (CDRs) to a database?

 

We are using custom code to write CDR-like data to log files and then later loading logs into a database.  We have very low usage right now, so I suspect that we could just write directly to the database.  But as we scale, is it a better idea to not write directly to the database?

 

Note I am not sure if we need custom CDRs or if FS' CDR module might be leveraged.  I have to look into that.

 

 

Robert



_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org