Re: inconsistent sesstion timeouts
Dale E. Reed Jr. ( (no email) )
Wed, 14 May 1997 01:40:22 -0700
Josh Hillman wrote:
>
> This user has Ascend-Maximum-Time = 32767. Any idea why the
> AcctSessionTime is so inconsistent with the following records (as well
> as
> longer than the max-time)? All of the following records have an
> AscendDisconnectCause = 100 (session timeout). Eventhough the
> protocol is
> set for MP, this user has only been using one channel per session--not
> 2 or
> more.
>
> CallDate AcctSessionTime
> --------------------------- ---------------
> May 6 1997 5:05PM 32866
> May 7 1997 8:37PM 32917
> May 8 1997 5:47AM 32890
> May 8 1997 3:00PM 32888
> May 9 1997 5:30PM 32932
> May 10 1997 2:39AM 32779
> May 10 1997 11:50AM 32811
> May 12 1997 5:18PM 32850
> May 13 1997 4:56PM 32852
>
> User's Radius settings (set via Emerald 2.1.11):
> User-Service: Framed-User
> Framed-Protocol: MP
> Ascend-Maximum-Time: 32767
> Ascend-Idle-Limit: 7200
>
> RadiusNT .60 running as a service in ODBC-only mode.
> SQL 6.5 running on same server as RadiusNT
> NT 4.0 SP2 + various hotfixes
> Ascend Max 4004 5.0Ai4
Sounds like the MAX might not be consistent in checking the timeleft
and booting the user. Some people have reported problems with negative
timeleft fields, and if the above is happening, they would definately
have negative timeleft fields in timebanking.
-- Dale E. Reed Jr. (daler@iea.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com