Ive talked to representatives of USR and they claim to have the same problem
with livingston radius 1.16, they told their clients to switch to the newer
livingston 2.0 that supports USR.
They claim this fixed the problem of no accounting update to the odbc link.
It seems, that if not properly setup, the radius server will incorrectly see
some extra data sent by the USR as 'bad authenticator'......(see previous
messages i sent)...
With other radius servers, they just programmed their radius servers to
ignore this data. Can we do this also for radius?
For more information about this list (including removal) go to: