[arm-allstar] Repeater Bounce

[Doug Crompton]

My question would be why would a node that did not key for 5 seconds after
the other end dropped even be useful? You would miss the first 5 seconds of
every transmission!

What you are doing is not uncommon and I suspect you are missing something.
Allstar will NOT ping/pong if it is in duplex=0 or nounkeyct=1.  You can
test this yourself. Key into your node with either of those set and it will
not respond back. Are you sure you are going into the repeater as a user
would?

In your case the tail of the repeater would keep Allstar keyed until it
drops. There is no way to avoid this unless you can shorten or eliminate
the repeater tail OR you can modify the repeater to output ONLY when input
PL is present to it. Your end will have COS valid whenever you node radio
sees valid PL from the repeater. When the repeater drops your end should
not respond back unless it is a one time telemetry message or someone
actually responding.


*73 Doug*

*WA3DSP*

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

On Sat, Feb 23, 2019 at 11:48 AM ddhcpracing <ddhcpracing at gmail.com> wrote:

> Doug,
>
> Yes, it at nounkey=1, and duplex=0, I understand boot. I was saying I
> tried everything. Is there a way for Allstar not to listen after it unkeys
> the link radio for 5 seconds?
>
> Thanks KG5RDF
>
> -------- Original message --------
> From: Doug Crompton via ARM-allstar <arm-allstar at hamvoip.org>
> Date: 2/23/19 10:25 AM (GMT-06:00)
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Cc: Doug Crompton <wa3dsp at gmail.com>
> Subject: Re: [arm-allstar] Repeater Bounce
>
> You need to figure out why it is ping/ponging. The usual reason in a
> situation like this is that the repeater end drops and the Allstar end
> responds back automatically and this continues on and on.  The Allstar end
> responding back is usually always the courtesy tone. You need to turn that
> off -
>
> nounkeyct=1
>
> in rpt.conf.  The thing I don't understand is that duplex=0 should also do
> this but is overkill in many cases as it turns off ALL telemetry.
>
> Setting rxondelay or hangtime to high numbers is not a good idea. Both
> would really screw up the way it would be intended to work. You need to put
> things back to default values. Only use either duplex=0 or the nounkeyct=1
> to start with and remember whenever you change any of these things you need
> to restart asterisk (astres.sh) for it to actually change.  With either
> duplex=0 or nounkeyct=1  Allstar should not respond back after receiving a
> transmission unless it is actually a real person coming back from a
> connection to that node.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Sat, Feb 23, 2019 at 11:10 AM "ddhcpracing via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > We have a RF hub failure. I have used Allstar to bring East and West
> bound
> > 24 repeater sites up in the meantime. I have one repeater I still need to
> > connect, to have full coverage in DFW. This site is being linked via rf
> to
> > a link radio v71 to Allstar.The issue is repeater bounce/pingpong. I
> need a
> > way for Allstar not to listen to the RF link for 5 seconds after it
> unkeys
> > the repeater.Tried two different nodes, hangtime 0-50000, Duplex 0,1,2,3,
> > and 4, and rxaudiodelay 0-26. Is there a variable I am missing to
> > accomplish this? Repeater site is not accessible and is dr1x. Done this
> > many times with no issue, but it's a vary far rf putt this time.Thanks
> > KG5RDF
> > _______________________________________________
> >
> > 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
> _______________________________________________
>
> 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
>