[RadiusNT] Incorrect "Acct-Session-Time" being logged

Josh Hillman ( (no email) )
Mon, 24 Jan 2000 21:28:23 -0500

Has anyone noticed unusually high Acct-Session-Time values for ISDN
customers, when dialing into Ascend Max units?

How's this for strange?:
Start of session: 1/24/00 3:10pm
End of session: 1/24/00 8:26pm
AcctSessionTime: 191786 seconds (over 53 hours)
The AcctSessionID for the start and stop records match
The session was a single 64k channel

Any ideas?? It doesn't seem to happen with all sessions--just some. I've
been noticing this strange behavior for a while now...

We're using a mix of Max 4048s, 4004, and 4002, all using TAOS 7.0.22 (the
latest version for the 4000 series); RadiusNT 2.5.206 running in ODBC mode
with SQL Server 6.5 SP5a.


For more information about this list (including removal) go to: