I think it is because there is no corresponding entry for session-timeout in the router. UserManager is probably your best bet. You can get support for it from this forum.
ADD: You might be able to disable/logout a user account with a scheduled script. Put the session-timeout value in comments and the use a script to disable the account and insure the client is logged off at the appropriate date/time. This may not be as easy as it appears at first. Much parsing and rearranging of the date will be required. You really require a Unix date/time stamp to do this. That allows the date/time to be a comparison. (< > =).
For example, today's date in my Linux server is
2010-09-04
and in Mikrotik
sep/04/2010
Thanks Tim, guys...
I'd like to use UserManager and I know it works great if you want to give someone say 4 hours.
As they'd log in at say 8:00 a.m. and be disconnected at 12:00 noon. Regardless of the session time, uptime etc...
But, I'm limited at the moment to 50 active users in UserManager with the license I have.
So, I'll need to create users in Hotspot, but I don't want them to be on for more than amount of time credited.
Now that I think about it. I believe this could be implemented very easily in Hotspot.
And it's this way by design, Mikrotik wants you to purchase the license which allows more users via UserManager.
You think?
I'll try your suggestions.
T