Re: RadiusNT and Calls Table

Steve Williams ( (no email) )
Fri, 12 Dec 1997 16:43:01 +1000

Is the AcctStatusID in the key for the table? I can't remember if ours is
or not since I am at home right now. Each SessionID, NASIdentifier and
AcctStatusType combination should be unique.

Sly (Steve Williams)

> No, it sends it for each START and STOP record...
> In other words, there is always TWO of them, one for the start and one
> the stop.
> At 04:23 PM 12/12/97 +1000, you wrote:
> >> 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
> >the
> >> duplicate SessionID, NASIdentifier, etc....I removed the 4 keys after
> >> backing up the table and everything is working wonderfully now, even
> >> 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.