[arm-allstar] Incorrect EchoLink Call

[John Huggins]

We have noticed this problem as well and here is the bad news...

It appears within the last year or more Echolink began supporting relay or
proxy servers.  These were put in place, along with a change in the code,
to support clients to connect outbound from certain private networks where
there wasn't support for routing back certain TCP/UDP ports without special
firewall NAT/port fwd rules.  I've used such proxy servers in the past to
access traditional Echolink systems with some success.

What this means HAMVOIP-Echolink...

Looking at our Echolink connection log through the Astreisk CLI, we see
numerous connects from an address range at amazonaws (107.23.x.x) as well
as IP's of private home users.  Users without relay/proxy resolve to a
proper call sign and node number when announced through the Echolink
module, but if you come through the proxy, a random call and node number
are announced.  We tried several time using an Android phone over the cell
network and came up as VA3RLL, KK4QVJ and W2SWX all with in a matter of a
few minutes / reconnects.  It appears the Echolink code must be scanning
the database for the IP and then reading back the call / #.  Since there
are numerous calls with the same IP, then it must pick the first it sees,
but that's just our guess.

Hence we have this feature turned off.

Not saying this describes your problem, but it appears to be a good
candidate for your symptoms.

John, kx4o

On Sun, Oct 8, 2017 at 8:25 PM, "Justin Grigg via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

>
>  Hello Group,
>
> I have a simplex node and enabled the option the that announces the
> connected EchoLink user’s phonetic call. The issue I am having is that it
> is announcing the incorrect call. Am I missing something?
>
>