Hello,
On 6 Nov 2012, at 23:53, Owen Lynch wrote:
> I've made some progress. It seems that dlg_manage() is required in the route
> script. Now I have CDR in syslog:
>
> NOTICE: acc [acc_cdr.c:192]: st=1352240307.196; et=1352240319.116; d=11.920
>
> but not as a RADIUS record. Looking at the
I've made some progress. It seems that dlg_manage() is required in the
route script. Now I have CDR in syslog:
NOTICE: acc [acc_cdr.c:192]: st=1352240307.196; et=1352240319.116; d=11.920
but not as a RADIUS record. Looking at the code I can only see syslog
support for CDR in the acc module, is t
Hi Paul,
yes, I have the standard acc parameters set up. I have RADIUS logging of
transactions working (start and stop events on call establishment and clear
down) but not CDR events. I understand that CDR support requires the dialog
module and I figure that the dlg_flag needs to be set and cleare
Hi Owen,
I think basically you are right. But referring to your code example, did
you set up the /log_flag/ module parameter correctly? E.g.:
#!define FLT_ACC 1
modparam("acc","log_flag", FLT_ACC)
Greetings,
Paul
On 06.11.2012 00:34, Owen Lynch wrote:
Hi,
I have transaction accounting to
