[arm-allstar] Still receiving "Un-authorized" messages on Echolink connection

[Mike Sullivan]

So, I have three separate nodes setup that I take care of currently, all
running latest software and all Pi 3B's. Node 1 is on cable internet at the
tower, node 2 is on cellular (AT&T) through a VPN, and node 3 is on
cellular (Verizon) through a separate VPN. When connecting to all three
nodes on Echolink from phone or computer, half the time I have no problem.
But the other half of the time, I still receive at least 1-3
"Un-authorized" messages before being able to connect. There's no set
pattern at all on how often it happens.

Allstar log shows the following line, and it comes up multiple times on the
unsuccessful attempts to connect:

[Nov  3 19:59:19] NOTICE[338] chan_echolink.c: Cannot find DB entry
for Callsign: KN4IMU, IP: @. Requesting DB update

I've had several members from both of the clubs (Nodes 1 and 2) say they
get this message often, and though they know why it's causing it and know
to keep trying, I feel like new users trying to connect are discouraged
from trying when they see the first "Un-authorized" message. There has to
be some sort of fix for this.. I know it's not the connections because I
have no other problems connecting out through Echolink, or in & out through
Allstar on any of the nodes.

For those interested in testing, the nodes in question on Echolink are
KN4IMU-L (personal simplex mobile), KG4DVE-R, and N8QA-R. If you get the
error, let me know the time and I will try to pull log. I do have verbosity
on KG4DVE-R turned up, I believe.

Mike