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

Doug Crompton wa3dsp at gmail.com
Sat Aug 24 00:57:56 EDT 2019 

More information below. We ran a test on this tonight using a Samsung phone
running echolink. The phone was connected and immediately an attempt was
made to connect to the Echolink server. You can see the phone makes an
attempt 5 times separated by just over 1 second from 30:45 to 30:51 or 6
seconds.  This is a phone timeout! Not Allstar. Then an attempt was made
immediately again at 31:11 or about 20 seconds later and it connected. This
is clearly a delay in Echolink updating the database. If the phone could be
made to try longer it would have been successful at probably 10-15 seconds.
This is NOT unreasonable. Our guess is the phone SW is causing this issue
and unless you can change the timeout on the phone you just need to
understand this and work around it. Waiting 15-30 seconds before attempting
the connect at cold start would solve the problem. Enough said!


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

testbench*CLI> echolink dbget callsign KB4FXC
Error: Entry for KB4FXC not found!
testbench*CLI>

[Aug 24 00:30:45] NOTICE[4113]: chan_echolink.c:2393 do_new_call: Cannot
find DB entry for Callsign: KB4FXC,  Requesting DB update.
    -- Received OK from Echolink server server2.echolink.org
    -- Received OK from Echolink server server1.echolink.org
    -- Directory pgm done downloading(partial,compressed), 78 records
[Aug 24 00:30:47] NOTICE[4113]: chan_echolink.c:2393 do_new_call: Cannot
find DB entry for Callsign: KB4FXC,  Requesting DB update.
    -- Received OK from Echolink server server1.echolink.org
    -- Received OK from Echolink server server3.echolink.org
    -- Directory pgm done downloading(partial,compressed), 585 records
[Aug 24 00:30:48] NOTICE[4113]: chan_echolink.c:2393 do_new_call: Cannot
find DB entry for Callsign: KB4FXC,  Request DB update.
    -- Received OK from Echolink server server1.echolink.org
    -- Received OK from Echolink server server1.echolink.org
    -- Directory pgm done downloading(partial,compressed), 12 records
[Aug 24 00:30:50] NOTICE[4113]: chan_echolink.c:2393 do_new_call: Cannot
find DB entry for Callsign: KB4FXC,  Requesting DB update.
    -- Received OK from Echolink server server1.echolink.org
    -- Received OK from Echolink server server2.echolink.org
    -- Directory pgm done downloading(partial,compressed), 17 records
[Aug 24 00:30:51] NOTICE[4113]: chan_echolink.c:2393 do_new_call: Cannot
find DB entry for Callsign: KB4FXC,  Request DB update.
    -- Received OK from Echolink server server3.echolink.org
    -- Received OK from Echolink server server1.echolink.org
    -- Directory pgm done downloading(partial,compressed), 27 records


<<<GOT "un-authorized" message in echolink client on phone>>>
<<<Tried to connect again from the phone>>>

[Aug 24 00:31:11] NOTICE[4113]: chan_echolink.c:2393 do_new_call: Cannot
find DB entry for Callsign: KB4FXC,  Requesting DB update.
    -- Received OK from Echolink server server1.echolink.org
    -- Received OK from Echolink server server1.echolink.org
    -- Directory pgm done downloading(partial,compressed), 61 records
    -- new CALL=KB4FXC,name=        samsung SM-S804VL User
    -- Executing [1211 at radio-secure:1] Rpt("echolink/el0-4", "1211|X") in
new stack
  == Spawn extension (radio-secure, 1211, 1) exited KEEPALIVE on
'echolink/el0-4'
    -- Received OK from Echolink server server1.echolink.org
    -- Received OK from Echolink server server2.echolink.org
    -- Directory pgm done downloading(partial,compressed), 388 records
    -- disconnect
    -- Hungup 'DAHDI/pseudo-1020771530'

On Sat, Aug 24, 2019 at 12:05 AM Doug Crompton <wa3dsp at gmail.com> wrote:

> Mike,
>
> The Hamvoip Echolink code will try indefinitely to update the database if
> a node is not in there. The problem is your end is apparently timing out
> trying to connect. In Windows I believe these times are settable I don't
> know about your phone application but the bottom line is that in most cases
> you cannot just connect to echolink and then immediately connect to where
> you want to go. You need to either wait for 30 seconds to a minute when you
> connect to echolink for your node information to propagate or be able to
> set your ends connect timeout so it would wait until it becomes available
> upon a connect. We have no control over how fast Echolink updates their
> database. You have to be patient period! I repeat that if you had been
> using the Hamvoip code before we added DNS and registration in many cases
> from a cold start you would have had to wait up to 15 minutes to do an
> Allstar connect. Many long time Allstar users remember this.
>
> The rtcptimeout is the number of hearbeats that are missed before a
> connection is timed out. This is set to 10 in our config which is 100
> seconds. Hearbeats are every 10 seconds. This has nothing to do with your
> connection problem. and should not be changed.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Fri, Aug 23, 2019 at 9:29 PM "Mike Sullivan via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> There’s no way to increase the connect before timing out period or
>> anything
>> like that? I feel like that would help it a lot. Yes, it’s a rare
>> occurance, but an annoying one.
>>
>> Nobody did answer my other question on rtcptimeout, by the way.
>>
>> On Fri, Aug 23, 2019 at 09:48 "Doug Crompton via ARM-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> > The only thing I can tell you at this point is come on line and wait a
>> > minute or two or maybe more to connect.  You know we use to have to
>> wait up
>> > to 15 minutes or more to do Allstar connects until we introduced DNS
>> lookup
>> > and Hamvoip registration and non Hamvoip user still have that wait. You
>> > also can use an Allstar method to connect rather than Echolink.
>> >
>> >
>> > *73 Doug*
>> >
>> > *WA3DSP*
>> >
>> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>> >
>> > On Fri, Aug 23, 2019 at 8:51 AM "Mike Sullivan via ARM-allstar" <
>> > arm-allstar at hamvoip.org> wrote:
>> >
>> > > I just tried it as I was pulling into the house after getting off
>> work,
>> > no
>> > > proxy, same thing, four in-sequence database update requests within
>> less
>> > > than 10 seconds then the unauthorized message. Next attempt, works
>> fine.
>> > > Method of connection is not the problem. It’s the Echolink database
>> not
>> > > being updated in time either by failing to be downloaded, or not
>> updating
>> > > fast enough to prevent an un-authorized message.
>> > >
>> > > Mike
>> > >
>> > > On Fri, Aug 23, 2019 at 01:53 "Doug Crompton via ARM-allstar" <
>> > > arm-allstar at hamvoip.org> wrote:
>> > >
>> > > > Try not using a proxy. Use you cell Internet, turn off wifi.
>> > > >
>> > > >
>> > > > *73 Doug*
>> > > >
>> > > > *WA3DSP*
>> > > >
>> > > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
>> >*
>> > > >
>> > > > On Fri, Aug 23, 2019 at 12:07 AM "Mike Sullivan via ARM-allstar" <
>> > > > arm-allstar at hamvoip.org> wrote:
>> > > >
>> > > > > That’s the point I was trying to make. The rate it happens is so
>> > > > inaccurate
>> > > > > that I don’t know if it’s an error on Echolink’s part, on the
>> > database
>> > > > > server, on the polling between Hamvoip and the Echolink database,
>> or
>> > > > what.
>> > > > > Sometimes I can immediately log in and have no problem at all
>> > > connecting,
>> > > > > even after not logging in to Echolink for days. Other times, I
>> can’t
>> > > log
>> > > > in
>> > > > > even after waiting X seconds, and as the logs show, either it
>> fails
>> > to
>> > > > get
>> > > > > the database and it checks the last received database, or my node
>> > > doesn’t
>> > > > > appear for whatever reason.
>> > > > >
>> > > > > That’s why I was also asking what rtcptimeout is for. Maybe it
>> just
>> > > needs
>> > > > > more time to receive a database update from the server before
>> > rejecting
>> > > > the
>> > > > > connection. I feel like anyone that is trying to connect to
>> Echolink
>> > &
>> > > > sees
>> > > > > that they’re unauthorized and thinks they aren’t welcome.
>> > > > >
>> > > > > Mike
>> > > > >
>> > > > > On Thu, Aug 22, 2019 at 23:32 "Doug Crompton via ARM-allstar" <
>> > > > > arm-allstar at hamvoip.org> wrote:
>> > > > >
>> > > > > > There was nothing changed in updates for quite awhile in
>> echolink
>> > so
>> > > I
>> > > > > > doubt that has anything to do with it. When your echolink node
>> > comes
>> > > > > online
>> > > > > > it will take a period of time for it to appear in the database.
>> > > > Echolink
>> > > > > > has had its share of connection problems on and off. Allstar
>> > attempts
>> > > > to
>> > > > > > update the database on connection several times. If it is not
>> there
>> > > > after
>> > > > > > that it fails but that does not mean you cannot try again a
>> minute
>> > or
>> > > > two
>> > > > > > later. This may also have something to do with proxy connections
>> > > which
>> > > > > may
>> > > > > > not always show up in our database.
>> > > > > >
>> > > > > >
>> > > > > > *73 Doug*
>> > > > > >
>> > > > > > *WA3DSP*
>> > > > > >
>> > > > > > *http://www.crompton.com/hamradio <
>> > http://www.crompton.com/hamradio
>> > > >*
>> > > > > >
>> > > > > > On Thu, Aug 22, 2019 at 11:27 PM "Steve Polley via ARM-allstar"
>> <
>> > > > > > arm-allstar at hamvoip.org> wrote:
>> > > > > >
>> > > > > > > Doug,
>> > > > > > >
>> > > > > > > I have ran into the problem occasionally also running the
>> latest
>> > > > > update.
>> > > > > > >
>> > > > > > > Steve
>> > > > > > > N0SWP
>> > > > > > >
>> > > > > > > On Thu, Aug 22, 2019 at 9:54 PM "Doug Crompton via
>> ARM-allstar" <
>> > > > > > > arm-allstar at hamvoip.org> wrote:
>> > > > > > >
>> > > > > > > > Mike,
>> > > > > > > >
>> > > > > > > >  Dave could give more details on this but from what you say
>> if
>> > > you
>> > > > > are
>> > > > > > > > getting the database then you should be registered with
>> > Echolink.
>> > > > It
>> > > > > > > sounds
>> > > > > > > > like that message would be issued if you were not
>> registered.
>> > Are
>> > > > you
>> > > > > > in
>> > > > > > > > the database that gets downloaded? Echolink has three
>> possible
>> > > > > > variations
>> > > > > > > > for your call - W3XYZ, W3XYZ-L, and W3XYZ-R. Each can have a
>> > > > > different
>> > > > > > > > password or they all can be the same only one can be used
>> per
>> > > > > distinct
>> > > > > > > > public IP address. At this time no one else has reported
>> this
>> > > issue
>> > > > > so
>> > > > > > it
>> > > > > > > > seems it might be connected to something going on within
>> your
>> > > > system.
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > *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
>> > > > > > > _______________________________________________
>> > > > > > >
>> > > > > > > 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
>> > > > > _______________________________________________
>> > > > >
>> > > > > 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
>> > > _______________________________________________
>> > >
>> > > 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
>> _______________________________________________
>>
>> 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