I had an Echolink connection from a user that was stuck on transmit. The user was using an Android version of Echolink. They believe they had closed the Echolink application on the Android. If true, that may mean a bug in ASL. Even if not true, it made me wonder…
Is there a timeout setting somewhere in ASL that can disconnect a node that transmits longer than some limit?
I believe the original poster is looking for a way to disconnect a node (echolink, in this case) that transmits over a certain point. Not just to drop transmitters. AFAIK, ASL3 doesn’t have a built-in way to deal with that, without using events and getting creative with scripts.
On my system, I use tbd for echolink, then bridge my ASL node to that. TBD gives much greater control of echolink than ASL does, including the ability to automute long transmissions.
In the unfortunate event you have several echolink stations connected, ASL isn’t aware of them, so doesn’t have to do a bunch of back-and-forth transcoding, so this results in better audio quality… or at least as good as echolink ever gets, which isn’t great.
It won’t integrate nicely into which ever mon you decide to use, though, so there’s that.
I would actually like to implement something like this for my parrot node (55553) for ASL connections. Sometimes, a misconfigured node can tie up the system for hours without my knowledge.
Someone sent me a code snippet a while back that should theoretically work, but I haven’t actually gotten around to trying it yet.