[arm-allstar] Echolink Question

[Anthony (N2KI)]

Steve. et al,

I do not believe I disabled connections in HAMVOIP.  The fix seems to have
been adding *PINGTEST* to the "allow list".  Echolink tech support was then
able to verify that the link was a viable one. The
only additional question they have is when a station cannot connect.  There
is no announcement indicating  a reason for the disallowance or rejection.
I checked in the Echolink.conf file and the RPT.conf file but did not see
any toggle switches to invoke  this, if it even exists.  So if anyone
knows, please bring it forth.  It will be a help.   Thanks!

Regards,

Anthony (N2KI)









On Tue, Apr 26, 2022 at 9:52 PM "Steve Agee via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> *Also, double check you did not disable incoming connections in HAMVOIP.
>
> N5ZUA
> *
> On 4/26/2022 5:01 PM, "Anthony (N2KI) via ARM-allstar" wrote:
> > Maybe someone has a bit of knowledge on the connectivity to an Echolink
> > node that is running on an Allstar node.
> >
> > I keep getting messages from Echolink Tech support telling me that my
> node
> > is not accessible.  Port forwarding is correct and I am able to connect
> to
> > it from the WAN side.  It seems to be working bidirectionally.
> >
> > Any idea why this could be happening?
> >
> > Regards,
> >
> > Anthony (N2KI)
> > _______________________________________________
> >
> > 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/4 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/4 web page - http://hamvoip.org
>