Re: RadiusNT and Calls Table

Mitch Wagers ( )
Thu, 11 Dec 1997 22:36:32 -0800

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 for
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 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)
> ----------------------------------------------------------
> RadiusNT Mailing List