[arm-allstar] Echolink "Un-authorized" connection messages

[Mike Sullivan]

I know how Echolink works in itself, I know the differences and what it
requires. Let me break it down because the point is being missed..

- I log in to Echolink on my phone, using my proxy at home.

- I go to connect to either our direct repeater node, or the neighboring
club’s repeater. Both running Hamvoip.

- The node doesn’t show me in the Echolink DB, so it requests a database
update

- Sometimes, it just takes one request for a DB update, and it shows me
online, and I connect successfully

- Sometimes, it can’t receive a database update first time so it seems to
request again several times. After several failed attempts, it isn’t able
to show me in the database and refuses my connection. <== THIS is where I’m
having issues. After another attempt or two at connecting, Echolink finally
shows me in the database, and I successfully connect.

So my assumption is, either Echolink is failing to update the database, or
it does not update fast enough to show me online and allow me to connect.
This does not happen when I connect to the bridge node, which is Echolink
on my Windows VDS, permanently connected to the node at the tower. Now,
when connecting to there, it does take a long time so maybe Echolink on
windows allows a longer update time before refusing connection, I’m not
sure.

I know there is a rtcptimeout=10 configuration in the Echolink file, which
i assume is 10 seconds, but I do not know what this is for, and no
documentation online shows it either.

If you want to try it out several times and see if you get an Un-authorized
message, the nodes are KG4DVE-L #348560 and N8QA-R #839665. Both are
running Hamvoip. The bridge node is KG4DVE-R #975506 running on Windows.
Give yourself a period of time between connections, log off Echolink etc.
If you get the Un-authorized message, send me a time and callsign and which
node, and I will pull the log for that time period.

Mike

(PS I wasn’t on Echolink when you did that. I am on it now, and just
connected fine)


On Thu, Aug 22, 2019 at 22:57 "Doug Crompton via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Also not sure if you have this online but I am not seeing your entry here -
>
> *CLI> echolink dbget c KN4IMU
> Error: Entry for KN4IMU not found!
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Thu, Aug 22, 2019 at 8:50 PM "Mike Sullivan via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> >  Back when I was first setting up our club's Allstar node, I was
> reporting
> > on an issue where Echolink would report that I was un-authorized to
> connect
> > to the node, but subsequent attempts, I was able to connect fine. I
> figured
> > this was just a fluke with our node, but I set up a second node at
> another
> > club's tower, which runs through an OpenVPN tunnel instead of a direct
> > cable connection. Both nodes have the same problem, just not constantly.
> > Most times I have no problem, but there will be the occasional time that
> it
> > fails to connect and says I'm un-authorized.
> >
> > In checking the Allstar log on either node after this happens, I see
> > multiple subsequent requests for a database update when it does fail. The
> > failed attempts are separated 2 seconds apart, and can be anywhere from
> 4-8
> > times I have seen, but always result in a failed connection. Other times
> it
> > is just a single DB update and no problem connecting. Running 'echolink
> > dbdump' in CLI produces a valid database.
> >
> > Could this be an issue on Echolink's database end, or is there something
> I
> > can do with Allstar to ensure the node updates more regularly? I can't
> find
> > any other evidence listed. I've attached copies of the logs below.
> >
> > Mike
> >
> > Failed attempt
> >
> > [Aug 22 19:45:16] NOTICE[27272] chan_echolink.c: Cannot find DB entry
> > for Callsign: KN4IMU, IP: H��v103.85.188. Requesting DB update.
> > [Aug 22 19:45:18] NOTICE[27272] chan_echolink.c: Cannot find DB entry
> > for Callsign: KN4IMU, IP:  ��v103.85.188. Requesting DB update.
> > [Aug 22 19:45:20] NOTICE[27272] chan_echolink.c: Cannot find DB entry
> > for Callsign: KN4IMU, IP: p��v103.85.188. Requesting DB update.
> > [Aug 22 19:45:22] NOTICE[27272] chan_echolink.c: Cannot find DB entry
> > for Callsign: KN4IMU, IP: н�v103.85.188. Requesting DB update.
> > Successful attempt
> >
> > [Aug 22 19:55:08] NOTICE[27272] chan_echolink.c: Cannot find DB entry
> > for Callsign: KN4IMU, IP: 0��v103.85.188. Requesting DB update.
> > _______________________________________________
> >
> > 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