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 would be unique it solve the problem at radius server level independent of broken UAs who are reusing Acct-Session-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:
- 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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serdev