pers of the AAA modules. Perhaps it
will come later.
John Quick
> From: "Jeff Kronlage"
> Subject: Re: [OpenSIPS-Users] Radius CDR records depend who hangs up
first
> To: "OpenSIPS users mailling list"
> Message-ID:
> Content-Type: text/plain;
st
> Subject: Re: [OpenSIPS-Users] Radius CDR records depend who hangs up first
>
> John,
> See if this helps.
>
> http://www.opensips.org/html/docs/modules/1.6.x/acc.html#id271094
>
> 1.5.5. detect_direction (integer)
>
> Controls the direction detection for s
John,
See if this helps.
http://www.opensips.org/html/docs/modules/1.6.x/acc.html#id271094
1.5.5. detect_direction (integer)
Controls the direction detection for sequential requests. If enabled
(non zero value), for sequential requests with upstream direction
(from callee to caller), th
---
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of John Quick
Sent: Wednesday, November 11, 2009 8:28 AM
To: users@lists.opensips.org
Subject: [OpenSIPS-Users] Radius CDR records depend who hangs up first
Using Opensips version 1.6.0 with radiusclient-ng and the
Using Opensips version 1.6.0 with radiusclient-ng and the new AAA modules for
authentication and
accounting. The radius server is configured to write CDR records to a MySQL
database. The records it
is writing to the table radius.radacct are sometimes merged into one record per
call, but other ti
