[arm-allstar] Echolink troubles
Douglas Goree
degforyou at gmail.com
Sun Oct 6 00:19:33 EDT 2019
I think it is *3309999 or *3350191
On Sat, Oct 5, 2019 at 6:30 PM "John Simmons via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
>
>
>
>
> David,
>
> I managed to solve the problem I posted about, it turned out to be a
> typo in the echolink.conf.
>
> However I several other questions about the Echolink setup and operation
> that I can't seem to find the answers to.
>
> 1. It seems that the Echolink telemetry only plays on the primary node
> on a Pi. Is there a way to make it play on another node simultaneously?
> 2. How do I make an Echolink connection from the radio side via DTMF?
> For example, the Echolink test node is 9999. Sending 9999 or *9999
> from the DTMF doesn't cause a connection. I've tried from both the
> primary node and a permanent connected node.
>
> A non-Echolink question: is there an Allstar test node? I hate to do a
> drive-by on a random node.
>
> Thanks for your tech support.
>
> -de John NI0K node 50191
>
>
> David McGough wrote on 10/1/2019 9:45 PM:
> > 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
> >>
>
>
> _______________________________________________
>
> 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