[arm-allstar] a very odd Echolink problem

[Dave Petrie]

can you tell me the echolink node number that you are trying to connect to
so i can try it using different choices
I can't find my notes but for some reason i remember i had to change the
Echolink password and then change it in rpt.conf
echolink.conf
to a twelve digit no special characters just letters and numbers all
capital letters


On Thu, Nov 16, 2023 at 8:06 AM Dustin Perdue via ARM-allstar <
arm-allstar at hamvoip.org> wrote:

> We have tried from four different devices and accounts. In all cases, the
> standard client could not connect, but everything else could, including
> RepeaterPhone as an echolink client.
>
> Sent from my zippo
>
>
> > On Nov 14, 2023, at 23:31, David McGough <kb4fxc at inttek.net> wrote:
> >
> > 
> > Patrick,
> >
> > Have you tried connecting from multiple Iphones, or just a single device?
> >
> > I know hams do use the Iphone/iOS apps sucessfully.
> >
> > 73, David K4FXC
> >
> >> On Tue, 14 Nov 2023, Dustin Perdue via ARM-allstar wrote:
> >>
> >> Right, but in this case, there is something going on node side. No
> >> matter what Public proxy you use, even if you use a relay or direct, the
> >> same thing happens. Yes, I did actually go direct, and forwarded the
> >> EchoLink ports from my phone to my Public IP, which is a bit of an odd
> >> thing to do.
> >> Sent from my zippo
> >
> >
> >> On Nov 14, 2023, at 21:37, Dave Petrie via ARM-allstar <
> arm-allstar at hamvoip.org> wrote:
> >>
> >> i have echolink on my iphone
> >> sometimes i have to click on settings then public proxy snd every time
> i touch the public proxy i get a different proxy and it connects much better
> >>
> >>
> >> Sent from my iPhone
> >>
> >>>> On Nov 14, 2023, at 8:27 PM, Patrick Perdue via ARM-allstar <
> arm-allstar at hamvoip.org> wrote:
> >>>
> >>> Those who know me well know that I am, by no means, a fan of echolink.
> >>>
> >>> A fellow blind ham has an interesting problem, which I've never seen
> before, and which I tried, unsuccessfully, to diagnose.
> >>>
> >>> On a system running the latest HamVoIP, if someone connects to his
> node through the stock iOS echolink client, the call stops progressing at
> >>>
> >>> exiting keep-alive... something. Sorry, I don't have a log, but I can
> get access to it later. Then the call times out on the phone client side.
> >>>
> >>> However, if a call comes in through Repeaterphone on iOS, or the
> echolink module on another HamVoIP node, the call progresses normally.
> >>>
> >>> HUH?
> >>>
> >>> What?
> >>>
> >>> and other such words.
> >>>
> >>> I am a very confused person.
> >>>
> >>> 73
> >>>
> >>> N2DYI
> >>>
> >>> _______________________________________________
> >>>
> >>> 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
> > _______________________________________________
> >
> > 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
>