[arm-allstar] Echolink troubles
David McGough
kb4fxc at inttek.net
Tue Oct 1 22:45:53 EDT 2019
John,
I guess echolink works from you call phone when connecting to other
echolink nodes? If so, this is likely a routing / NAT issue with traffic
to or from node 50191.
How does node 50191 get Internet Access? Also, can any other echolink
user connect to node 50191, or is it broken for everyone?
73, David KB4FXC
On Tue, 1 Oct 2019, "John Simmons via ARM-allstar" wrote:
> I have 3 nodes connected together permanently, two are a split site vhf
> and the third is a uhf link radio. The only public node is the vhf
> transmit, which is the second node on the Pi.
>
> I (think) followed the directions on setting up Echolink on the public
> node, 50191. If I try to connect via cell I get a 'timed-out' error but
> the uhf link radio announces a connection with the Echolink node number
> and the Allstar node number. The callsign is not announced despite my
> setting=3 in rpt.conf. A second connection attempt from the cell doesn't
> announce on any radio and the cell shows timed out again.
>
> Suggestions please?
>
> -de John NI0K
> _______________________________________________
>
> 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
>
More information about the ARM-allstar
mailing list