Re: RadiusNT and Calls Table

Mitch Wagers ( )
Thu, 11 Dec 1997 22:53:15 -0800

Ok, I can tell you two things really quick....
There is a SessionID in the START record (acctstatustype=1) and a SessionID
in the stop record (acctstatustype=2), those are identical and that IS
correct, yes?

At 10:50 PM 12/11/97 -0800, you wrote:
>Mitch Wagers wrote:
>> Ok...I have a question....
>> 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 the
>> 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 definition of a key for a DB is something that uniquely identifies
>that record from all other records. If you remove the key, I can
>almost gurantee that you will have multiple entries in the calls
>table for the same call. That IS NOT something you want if
>you are going to do billing.
>Find out WHY you are getting duplicate accounting records, don't
>just remove the key. Is a NAS using to low of a timeout? Are you
>using and old RadiusNT with a NAS that requires signed accounting
>packets? Those are the kind of things that will cause this.
>Dale E. Reed Jr. (
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today |
> ----------------------------------------------------------
> RadiusNT Mailing List