I thought I had this problem taken care of when I reinstalled the calls
trigger, but apparently it had no effect.
Stop records are being inserted into the Calls table with no problems, but
it's not reaching the CallsOnline table.
I DID notice that the NASIdentifier is sometimes different with the stop
record, so it doesn't match up with the NASIdentifier with the start record.
Could this be causing the problem? If so, how might I get around this
> 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: