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