[arm-allstar] Echolink call sign issue

[James R. Pilgram]

I believe LSNODES shows echolink nodes and that was where you saw it.  

Jim
NH6HI 


  Original Message  
From: arm-allstar at hamvoip.org
Sent: December 21, 2018 07:23
To: arm-allstar at hamvoip.org
Reply-to: arm-allstar at hamvoip.org
Cc: laroy.mccann at gmail.com
Subject: Re: [arm-allstar] Echolink call sign issue

Ok, I guess I have been working way too much lately!!!!
I sure thought the stats server showed the callsign.  My bad.

I am looking forward to being off ALL next week.  Maybe that will clear my
head. LOL

73's and I hope everyone has a Merry Christmas.
LaRoy McCann, K5TW

On Fri, Dec 21, 2018 at 11:01 AM "Doug Crompton via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> The extra leading “3” indicates to AllStar that it is an Echolink node
> number.
>
> It is not a bug.
>
>
>
> Paul / KN2R
>
>
>
> The stats.AllStarlink.org web site *never* had the ability to report
> Echolink callsigns in their database!
>
> So the bubble chart has *always* showed “Not in database”.
>
>
>
> Paul / KN2R
>
>
>
>
>
> ---------- Forwarded message ---------
> From: *"LaRoy McCann via ARM-allstar"* <arm-allstar at hamvoip.org>
> Date: Fri, Dec 21, 2018 at 9:56 AM
> Subject: Re: [arm-allstar] Echolink call sign issue
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Cc: LaRoy McCann <laroy.mccann at gmail.com>
>
>
>
> Doug,
> Ok, I think this is the issue.
>
> When I connect with my iphone to my hamvoip node via echolink, Supermon is
> showing my echolink node as 3347194.  My echolink node is actually 347194.
>
> I believe there is a bug in the hamvoip code that is not stripping the
> leading "3" from the echolink node number before it is passed to the stats
> server.  That is why the stats server does not know the callsign of the
> node number it is displaying.
>
> Can you see if you can replicate this issue?
> Thanks
>
> On Thu, Dec 20, 2018 at 5:17 PM LaRoy McCann <laroy.mccann at gmail.com>
> wrote:
>
> >
> > Ok, I see it doing the partial downloads from the echolink servers.
> > That's ok.
> >
> > Yes, I am online with K5TW and connected to K5TW-R.
> >
> > If you look at www.nearlug.org you will see my Supermon page.  It shows
> > my call 'K5TW' connected.
> > If you look at the link for 41741 or the bubble chart you will see the
> > stats server knows my echolink node number but it don't know the
> callsign.
> > I guess that is a problem with the stats server not having my callsign in
> > it's database.
> >
> > On Thu, Dec 20, 2018 at 5:00 PM "Doug Crompton via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> 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>*
> >>
> /arm-allstar <
> 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