Idle timers seem to have a random bug from 3.3.1 and up - we know about it.
But since there is a workaround (put the idle timer in RADIUS or the users
table) we've been working on higher priority issues right now, like the
PM-2eR WAN port fix, the disconnect debugging, etc - things that will
cause a loss of service on their own. We are not ignoring it, just trying
to set priorities based on severity. The WAN port is fixed, so we'll be
moving on down the line.
We had started working on it a couple of weeks ago, but then we had the
breakthrough on the WAN port bug and it got idled as that was chased down
to the end.
-MZ
-- Although I work for Livingston Enterprises Technical Support, I alone am responsible for everything contained herein. So don't waste my managers' time bitching to them if you don't like something I've said. Flame me. Phone: 800-458-9966 support@livingston.com <http://www.livingston.com/> FAX: 510-426-8951 6920 Koll Center Parkway #220, Pleasanton, CA 94566