MZ> Not really, you can busy modems out one by one...
In my situation, this is impractical since "set Mx off" knocks off
the current user (or the one(s) that got in since you last looked).
With PRIs in a rotor style hunt group with reasonable activity, it's
impossible to busy out modems without inadvertently resetting
customers. Plus, there's no documented way to busy out Sx ports and
thereby deny ISDN calls.
I believe this request could be mostly accomplished by implementing
the "soft busy" feature that I've asked for previously.
MZ> Could be an idea though:
MZ> 'softreboot'
Please, please, please get "soft busy" out the door first. And verify
that it can be applied to Sx ports as well as Mx ports.
MZ> Busies out modems as they drop, and doesn't accept any new
MZ> connections (returns busy). Reboots when all connections are
MZ> gone.
MZ> maybe 'softreboot [seconds]'
MZ> Does the above, or after 'seconds' have passed says "Oh hell" and
MZ> just reboots anyway even if someone is on. That way some camped
MZ> out user can't keep the box from rebooting.
MZ> Maybe 'softreboot [users (number)] [seconds (value)] is better.
MZ> Waits for them all to clear. Unless a 'users value' pair is
MZ> present - waits for it to drop to this number (what, only 5 left -
MZ> reboot). And/or a 'seconds value' pair - waits that number of
MZ> seconds...
MZ> This is me, thinking...
Not wanting to sound like a broken record, but... With a "soft busy"
feature, an expect script could provide the above options. (I really
like the options, btw.)