[OpenSIPS-Users] Radius CDR records depend who hangs up first

[Zahid Mehmood]

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), the FROM and TO will be swapped (the  
direction will be preserved as in the original request).

It affects all values related to TO and FROM headers (body, URI,  
username, domain, TAG).

Default value is 0 (disabled).

Example 1.5. detect_direction example

modparam("acc", "detect_direction", 1)


--
Zahid


On Nov 11, 2009, at 10:27 AM, John Quick wrote:

> 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 times
> appear as two records per call.
>
> The scenario for my test calls is:
> Remote IP phone ----> Opensips  ---->  Gateway  ---->  Carrier  ---- 
> > mobile phone
>
> The device making the call and the dialled number are identical -  
> all that is different is the person
> who hangs up first. Only when the called party (mobile phone) hangs  
> up first do I get two CDR records.
> These records both have the same Call-ID (shown in the field  
> AcctSessionID).
>
> Is this behaviour expected or does it indicate some kind of  
> configuration problem?
>
> John Quick
> Smartvox Limited
> Web: www.smartvox.co.uk
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users