[Serusers] Radius accounting unreliable

[AG Support]

RadAcctId is indeed unique because is auto-increment column from mysql. 
Radius server has however no knowledge about this unique id when making 
an update because is not present in the START or STOP packet.

The unique key used by default by radius radacct table is made of:

Acct-Session-Id
Acct-Unique-Session-Id

Acct-Session-Id should be unique but is = SIP callid and when coming 
from buggy phones it's not.
Acct-Unique-Session-Id should also be unique but sometimes is not. It 
is server generated so it could be easily corrected.

Does anyone know where is Acct-Unique-Session-Id  generated?

SER, Radius client or Radius Server?

On Jun 2, 2004, at 9:13 PM, Juha Heinanen wrote:

> AG Projects support writes:
>
>> For those relying on Radius accounting generated by SER beware that 
>> the
>> combination of RadAcctId-AcctSessionId is not at all unique.
>
> in my table RadAcctId in primary key and thus must be unique.  also, i
> have spit radacct table to three tables: radstart, radstop. and
> radmissed, becaus i don't like the idea of update.
>
> -- juha