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)
2. The Acct-Unique-Session-Id is not unique either, it repeats itself
every now and then.
I would appreciate to see reactions for this problem from the
developers.
Regards,
Adrian