[arm-allstar] timed link disconnect from receiving node

[Doug Crompton]

Lawrence,

   All of this stuff could be done with an external script as everyone has
different needs. I have written many scripts to do different things in
Allstar and the current thought is to do it this way rather than put every
little feature in Allstar itself. It makes it much easier for users to
modify it to their liking and is independent of the base code.

In your case you would look for a connect from that specific (WX) node and
give it three minutes and then disconnect it. This could be easily done in
a script but doing it as an overall connection monitor where you look at
how long a node has been inactive and selectively do it is a little more
complicated.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Fri, May 17, 2019 at 12:51 AM "Lawrence Roney via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> We have a club member who was looking to do the same thing with their
> "weather" node.  The node's audio input comes from a receiver that's tuned
> to the regional NOAA weather broadcast loop.  As a safeguard, they asked me
> if there was a way to force disconnect an incoming call after 3 minutes,
> which is enough time to hear the loop broadcast in its entirety, but then
> drop the link so it could not inadvertently tie up a repeater.
>
> Thanks Doug,
>
> Lawrence - N6YFN
>
> ------------------------------
> Message: 2
> Date: Thu, 16 May 2019 01:10:06 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] timed link disconnect from receiving node
> Message-ID:
>         <
> CAMp6vssQ+4aXj9ZRLeg3eqM0KKypo2r6L_o3n_FcxVYv3HmBcw at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Butch,
>
>  First of I must point out we are not DMR. If someone connects somewhere
> and they are not causing a problem in my opinion it would be impolite to
> disconnect them. I see no reason to do that in most situations. Many people
> connect and are lurkers which is fine. It would also raise all kinds of
> questions as to why it happened. The network or Allstar would be blamed for
> disconnects unless you somehow made it clear that this would happen after
> so much inactive time. Also the Allstar reconnect feature of permanent
> connects could override it. In other words if you had a disconnect time out
> either internally or in a script someone else could have a reconnect. There
> is really no reason why someone can't stay connected. My combined hubs have
> 50-60 connects on a daily basis and others have more without problems.
> Most are permanent connects so if the hub resets they all reconnect within
> a few seconds.
>
> My question would be why would you want to do this? What purpose would it
> have in Allstar?
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Thu, May 16, 2019 at 12:51 AM "Butch Herring via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Is there a way for a "connected to" node to automatically disconnect a
> > "connected from" node after a certain length of time without affecting
> > other ongoing connections? I'm pretty sure I understand the way
> > lnkactenable and lnkacttime affect the node where the connect
> > originated from... i.e., lack of activity after a period of time such
> > as driving out of range, etc. However, I haven't figured out a way for
> the "connected to"
> > node to initiate a disconnect after a certain period of inactivity.
> >
> > To further clarify my question, consider how the Brandmeister DMR
> > network handles dynamic talk-group connections, whereby the connection
> > is automatically broken after fifteen minutes of inactivity.
> >
> > Butch, W5BE
> > _______________________________________________
>
>
>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>