[arm-allstar] Echolink call sign issue
LaRoy McCann
laroy.mccann at gmail.com
Thu Dec 20 17:57:25 EST 2018
My echolink servers resolve but don't respond to pings.
The echolink.conf files are ok on both systems and both systems show "ON"
status on the echolink website.
There is a long list from echolink dbdump and my hamvoip echolink node
'K5TW-R' is in there but not K5TW.
How does the echolink user that is connecting to the hamvoip echolink node
get their callsign sent to the allstar stats server to be displayed?
Supermon is showing it on the main screen but when I click on the bubble
chart, the bubble chart does not know what the callsign is of the echolink
user.
On Thu, Dec 20, 2018 at 4:24 PM "Doug Crompton via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> Well obviously your Echolink database is not updating. Check your
> echolink.conf file and make sure your password and servers selected look
> good. I am using the following here...
>
> server1=server1.echolink.org
> server3=server3.echolink.org
> server2=naeast.echolink.org
>
> Looking at my logs there are random lookup problems in the last month or
> two.
>
> In your client you should see a very long list doing -
>
> echolink dbdump
>
> Also not sure if the echolink servers return pings I thought they use to
> but none are from here at the moment here.
>
> [root at 29014-HUB ~]# ping server1.echolink.org
> PING server1.echolink.org (174.129.36.165) 56(84) bytes of data.
>
> --- server1.echolink.org ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 3126ms
>
> [root at 29014-HUB ~]# ping server2.echolink.org
> PING server3.echolink.org (174.129.209.125) 56(84) bytes of data.
>
> --- server3.echolink.org ping statistics ---
> 3 packets transmitted, 0 received, 100% packet loss, time 2105ms
>
> [root at 29014-HUB ~]# ping server3.echolink.org
> PING server3.echolink.org (174.129.209.125) 56(84) bytes of data.
>
> --- server3.echolink.org ping statistics ---
> 6 packets transmitted, 0 received, 100% packet loss, time 5218ms
>
> [root at 29014-HUB ~]# ping server4.echolink.org
> PING server4.echolink.org (50.18.55.39) 56(84) bytes of data.
>
> --- server4.echolink.org ping statistics ---
> 10 packets transmitted, 0 received, 100% packet loss, time 9393ms
>
> [root at 29014-HUB ~]# ping server5.echolink.org
> PING server5.echolink.org (68.178.144.151) 56(84) bytes of data.
>
> --- server5.echolink.org ping statistics ---
> 8 packets transmitted, 0 received, 100% packet loss, time 7280ms
>
> [root at 29014-HUB ~]# ping server6.echolink.org
> PING server6.echolink.org (54.161.182.37) 56(84) bytes of data.
>
> --- server6.echolink.org ping statistics ---
> 7 packets transmitted, 0 received, 100% packet loss, time 6219ms
>
> [root at 29014-HUB ~]# ping server7.echolink.org
> PING server7.echolink.org (54.93.96.123) 56(84) bytes of data.
>
> --- server7.echolink.org ping statistics ---
> 5 packets transmitted, 0 received, 100% packet loss, time 4175ms
>
> [root at 29014-HUB ~]# ping servers.echolink.org
> PING servers.echolink.org (174.129.209.125) 56(84) bytes of data.
>
> --- servers.echolink.org ping statistics ---
> 5 packets transmitted, 0 received, 100% packet loss, time 4147ms
>
> [root at 29014-HUB ~]# ping backup.echolink.org
> PING server6.echolink.org (54.161.182.37) 56(84) bytes of data.
>
> --- server6.echolink.org ping statistics ---
> 5 packets transmitted, 0 received, 100% packet loss, time 4183ms
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
>
> On Thu, Dec 20, 2018 at 4:44 PM "LaRoy McCann via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Hey Doug,
> >
> > K5TW-R is the echolink call sign on my hamvoip node.
> > I also have K5TW for personal use on my phone. I do connect to K5TW-R
> from
> > K5tw. These are separate ip addresses.
> >
> > Since this has started, Supermon or the allstarlink.org site does not
> show
> > the call sign of the echolink connection.
> >
> > Also, I only noticed this in the last 3-4 weeks, since I had updated both
> > system to the latest versions of hamvoip.
> >
> >
> > Here are some additional logs.
> >
> > [Dec 8 21:47:31] ERROR[359] chan_echolink.c: Failed to resolve Echolink
> > server server1.echolink.org
> > [Dec 8 21:47:31] ERROR[361] chan_echolink.c: Failed to resolve Echolink
> > server server1.echolink.org
> > [Dec 9 00:09:57] ERROR[361] chan_echolink.c: Error in parsing header on
> > server1.echolink.org
> > [Dec 9 11:10:04] NOTICE[360] chan_echolink.c: Cannot find DB entry for
> > Callsign: W5RZM, IP: 76.11.215.97. Trying to update database!
> > [Dec 10 01:15:31] ERROR[361] chan_echolink.c: Error in directory download
> > on server2.echolink.org
> > [Dec 10 11:40:03] NOTICE[360] chan_echolink.c: Cannot find DB entry for
> > Callsign: KG5LWF, IP: 44.190.9.223. Trying to update database!
> > [Dec 14 08:07:53] NOTICE[360] chan_echolink.c: Cannot find DB entry for
> > Callsign: K5TW, IP: 96.43.57.241. Trying to update database!
> > [Dec 20 14:06:59] NOTICE[9446] chan_echolink.c: Cannot find DB entry for
> > Callsign: K5TW, IP: 96.43.57.241. Trying to update database!
> > [root at k5tw-41741 asterisk]#
> >
> >
> >
> > Here is another group's system that is having the same issue.
> >
> > [Dec 10 01:15:59] ERROR[13589] chan_echolink.c: Error in directory
> download
> > on server1.echolink.org
> > [Dec 10 01:16:24] ERROR[13589] chan_echolink.c: Error in directory
> download
> > on server2.echolink.org
> > [Dec 14 07:53:03] NOTICE[13588] chan_echolink.c: Cannot find DB entry for
> > Callsign: K5TW, IP: 75.145.166.76. Trying to update database!
> > [Dec 14 10:44:07] NOTICE[13588] chan_echolink.c: Cannot find DB entry for
> > Callsign: TA2EJ, IP: 44.137.75.240. Trying to update database!
> > [Dec 15 12:05:10] NOTICE[13588] chan_echolink.c: Cannot find DB entry for
> > Callsign: KG5TCN, IP: 44.190.12.82. Trying to update database!
> > [Dec 18 18:33:10] NOTICE[13588] chan_echolink.c: Cannot find DB entry for
> > Callsign: N5ASH, IP: 44.190.9.221. Trying to update database!
> > [Dec 18 18:37:38] NOTICE[13588] chan_echolink.c: Cannot find DB entry for
> > Callsign: N5SEB, IP: 44.190.9.225. Trying to update database!
> > [Dec 18 18:37:40] NOTICE[13588] chan_echolink.c: Cannot find DB entry for
> > Callsign: N5SEB, IP: 44.190.9.225. Trying to update database!
> > [Dec 18 18:37:42] NOTICE[13588] chan_echolink.c: Cannot find DB entry for
> > Callsign: N5SEB, IP: 44.190.9.225. Trying to update database!
> > [Dec 18 18:37:44] ERROR[13588] chan_echolink.c: Cannot find DB entry for
> > Callsign: N5SEB, IP: 44.190.9.225
> > [Dec 18 18:37:45] NOTICE[13588] chan_echolink.c: Cannot find DB entry for
> > Callsign: N5SEB, IP: 44.190.9.225. Trying to update database!
> > [root at k5nea-46383 asterisk]#
> >
> >
> >
> > On Thu, Dec 20, 2018 at 3:29 PM "Doug Crompton via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > LaRoy,
> > >
> > > Looks fine here. Are you sure it is not K5TW-R ???
> > >
> > > 27225-HUB*CLI> echolink dbget c K5TW-L
> > > Error: Entry for K5TW-L not found!
> > > 27225-HUB*CLI> echolink dbget c K5TW-R
> > > 347194|K5TW-R|96.43.56.40
> > > 27225-HUB*CLI> echolink dbget c WA3DSP-L
> > > 147090|WA3DSP-L|67.165.29.63
> > > 27225-HUB*CLI> echolink dbget c K5TW
> > > Error: Entry for K5TW not found!
> > > 27225-HUB*CLI>
> > >
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >
> > > On Thu, Dec 20, 2018 at 4:01 PM "LaRoy McCann via ARM-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > When a user connects via echolink, their call sign is not found in
> the
> > > > database.
> > > >
> > > >
> > > > * NOTICE[9446] chan_echolink.c: Cannot find DB entry for Callsign:
> > K5TW,
> > > > IP: xx.xx.xx.xx. Trying to update database!*
> > > >
> > > > Looks like any echolink user trying to connect will get this message.
> > > >
> > > > I am seeing this on 2 different systems that I updated. I am not sure
> > > what
> > > > database it is looking for.
> > > >
> > > > LaRoy McCann - K5TW
> > > > _______________________________________________
> > > >
> > > > 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