Re: [SR-Users] Simple Call Accounting

2010-08-09 Thread Graham Wooden
I appreciate yours and Alex's' input and insight. While I don't have a many to one (proxy to DB), but rather one to one, I have a few worker scripts from a central reporting box that pulls those records and anything in the missed_calls and dialog and wraps up any collation. I don't use anything in

Re: [SR-Users] Simple Call Accounting

2010-08-09 Thread Uriel Rozenbaum
Just as an addendum to Alex's comment, I'm doing the exact same thing with MySQL triggers. Most strange situations can be worked around using some parameter in ACC or DIALOG modules (if working together). Our main cause is that we have many proxies and a central DB, so the work is performed by on

Re: [SR-Users] Simple Call Accounting

2010-08-08 Thread Alex Balashov
For comparison and contrast: We handle this in PostgreSQL by having Kamailio write to the 'acc' table, and adding triggers that operate on 'acc' events and populate or update another table, 'cdr', with actual CDRs in the desirable one-row-per-call way. The advantage to doing it that way versu

[SR-Users] Simple Call Accounting

2010-08-07 Thread Graham Wooden
Hi there, I wanted to share with the folks on this list a simple way to get some simple call accounting. My goal was to have a simple, one line in a DB entry, depicting when the call started (epoch and date/time), when the call ended (epoch and date/time), the call-to number and the calling-from,