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
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
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
