I could understand how the source IP would be different (proxy), but not
NAS Identifier. Real wierd. :(
NAS Identifier is a key requirement is tracking whos on. You might be
to modify the trigger to handle a stop differently, based on the
Acct-Session-ID or something.
> > Josh Hillman wrote:
> > >
> > > We're having a problem with users not being cleared in the CallsOnline
> > > when they disconnect, but the stop record IS received and does get
> > > into the Calls table without any problems. This is causing RadiusNT to
> > > reject sessions because it thinks the users are still online eventhough
> > > they're not.
> > > The sessions are only coming from specific NASes (via AT&T) and are
> > > associated with new Servers entries made last week.
> > > Unfortunately, there's no way to implement SNMP concurrency checking
> > > these NASes.
> > >
> > > What would cause this?
> > > How can it be fixed?
> > The trigger ignores older records than the current one in the
> > ServerPorts. If there are some delays, it could cause the
> > record to not make it into the ServerPorts table.
> For more information about this list (including removal) go to:
Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart