[arm-allstar] Echolink Question

[Anthony (N2KI)]

This issue was resolved by putting *PINGTEST* in the white list if you
have one active.

On another Echolink Support request, they were asking me the following.


*Does the software you're using provide the option of returning an
"accessdenied" message to a callsign that's not permitted?*

Also, I recall that I used to hear the call signs of stations connecting.
But that is not happening anymore.  I did check the RPT.conf file for
"eannmode=2 and that is present in the file.

Is there another switch to turn on?

Regards,

Anthony (N2KI)









On Tue, Apr 26, 2022 at 6:01 PM Anthony (N2KI) <n2ki.ham at gmail.com> 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)
>
>
>
>
>
>
>
>