[Serusers] Re: [Serdev] Radius accounting unreliable

[Jan Janak]

It is generated by the radiusclient library. I found the following using
google:

http://lists.cistron.nl/pipermail/freeradius-devel/2002-September/003530.html

Maybe you could find some solution if you google more.

  Jan.

On 02-06 15:37, Adrian Georgescu wrote:
> We do that "as a dirty trick " but looking in my statistics those tags 
> are repeating themselves at a far higher rate than Radius ids. It seems 
> a matter of luck of having a unique combination.
> 
> If Acct-Unique-Session-Id had been unique it would solve the problem at 
> RADIUS server level independent of broken UAs who are reusing 
> Acct-Session-Id (the SIP call id).
> 
> Do you know where is the Acct-Unique-Session-Id generated, is it radius 
> client or SER ?
> 
> Adrian
> 
> On Jun 2, 2004, at 3:01 PM, Jiri Kuthan wrote:
> 
> >At 01:36 PM 6/2/2004, AG Projects support wrote:
> >>Guys,
> >>
> >>For those relying on Radius accounting generated by SER beware that 
> >>the combination of RadAcctId-AcctSessionId is not at all unique.  If 
> >>you use MySQL for storage of radius accounting you will miss CDRs 
> >>every now  and then (because is a unique index) and the update 
> >>queries will update calls from the past as a result, calls with huge 
> >>duration are being generated.
> >>
> >>The problem is generated by a combination of factors:
> >>
> >>1. Some UAs reuse same call id among multiple calls (Grandstream 
> >>systematically show this behaviour)
> >
> >Indeed, that's why serweb uses combination of callid with from and 
> >to-tags
> >for accounting, something  similar can be certainly used with 
> >Radius+mysql.
> >
> >-jiri
> >
> >_______________________________________________
> >Serdev mailing list
> >serdev at lists.iptel.org
> >http://lists.iptel.org/mailman/listinfo/serdev
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers