[arm-allstar] Echolink call sign issue
Doug Crompton
wa3dsp at gmail.com
Thu Dec 20 18:00:13 EST 2018
LaRoy,
These are the kinds of messages you should see in the Asterisk client,
each message about every 5 minutes. This is with verbose=4 which is the
default coming from the menu -
-- Received OK from Echolink server naeast.echolink.org
-- Received OK from Echolink server server3.echolink.org
-- Directory pgm done downloading(partial,compressed), 541 records
-- Received OK from Echolink server server3.echolink.org
-- Received OK from Echolink server server3.echolink.org
-- Directory pgm done downloading(partial,compressed), 401 records
-- Received OK from Echolink server server3.echolink.org
-- Directory pgm done downloading(partial,compressed), 512 records
The Echolink database is stored in memory and not in a file you can access.
You can view it it the client with echolink dbdump or dbget. You can also
dump it to a file to examine in this way at the Linux prompt -
asterisk -rx "echolink dbdump" > some-directory/some-file
The database is not downloaded in entirety at each update. Only changes are
downloaded as you can see by the number of records updated. I just did this
and here are the results -
# wc -l /tmp/echolink
5622 /tmp/echolink
The problem often is that Echolink users expect to be able to connect
immediately upon turning on their Echolink on a phone or whatever. We made
some changes interrogating the data base when there is a connect to make
this update time faster but there still can be a delay before connection is
possible.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Thu, Dec 20, 2018 at 5:23 PM "LaRoy McCann via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> Ok, so it is not giving me an error message now in the hamvoip logs and it
> shows thte correct callsign on the supermon page, but when you click on the
> supermon node number it shows N/A for callsign or buble chart link shows
> not in database.
>
> On Thu, Dec 20, 2018 at 4:08 PM LaRoy McCann <laroy.mccann at gmail.com>
> wrote:
>
> > Doug,
> > I just tried it again and now it is working. Not sure what's up with
> that.
> > What database is the error messages referring to?
> >
> > On Thu, Dec 20, 2018 at 3:37 PM LaRoy McCann <laroy.mccann at gmail.com>
> > 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
>
More information about the ARM-allstar
mailing list