AscendMaximumTime 32767 second limitation

Josh Hillman ( (no email) )
Thu, 24 Apr 1997 11:00:49 -0400

Is it "normal" for an Ascend-Maximum-Time to be limited to <= 32767
seconds?
This limits the max session duration from 0 to 32767 seconds (2^15
possibilities).

32767 seconds = 9 hours, 6 minutes, 7 seconds

Setting Ascend-Maximum-Time > 32767 causes an incoming call to be
disconnected as soon as the login is authenticated. The
Ascend-Disconnect-Cause in the stop record = 100 = "session timeout." If
Ascend-Maximum-Time is within the 32ksec range and the caller is
disconnected for that reason, the Ascend-Disconnect-Cause is the same 100.

Is this a problem/limitation/setting lurking around in the Max 4004
(5.0Ai4) or is it in RadiusNT .60, or in SQL 6.5?

RadiusNT .60 (service, ODBC mode only)
Emerald 2.1.11
SQL 6.5
Ascend Max 4004 5.0Ai4

Thanks,

Josh Hillman
hillman@talstar.com