Re: RadiusNT and Calls Table

Steve Williams ( (no email) )
Fri, 12 Dec 1997 16:23:28 +1000

> The radius database (radius7.mdb) has 4 Primary Keys on the Calls
> table...Why is this so? We are getting tons of accounting errors due to
> duplicate SessionID, NASIdentifier, etc....I removed the 4 keys after
> backing up the table and everything is working wonderfully now, even have
> CallerID and NASPortDNIS working correctly....any ideas?

The SessionID for a particular NASIdentifier should never be duplicated.
This is a NAS issue and the SessionID's it sends for each call.

Sly (Steve Williams)