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

[Mike Sullivan]

 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.