[arm-allstar] Echolink Connection Telemetry

Doug Crompton wa3dsp at gmail.com
Sun May 28 23:16:54 EST 2017


First of all echolink is not a high priority. It is an add-on and our
mission is Allstar NOT echolink. That being said there is a very simple way
to determine if a node is in the database. Do the following after your
system has been up for awhile and has established the echolink database -

asterisk -rx "echolink dbdump" > /tmp/echolink.txt

Less /tmp/echolink/txt

You will be able to scroll through the list. If you want to look for a
specific call or node do

grep <call/node> /tmp/echolink.txt

[root at Pi3-test]# grep 147090 /tmp/echolink.txt
147090|WA3DSP-L|67.165.29.63

[root at Pi3-test]# grep WA3DSP /tmp/echolink.txt
147090|WA3DSP-L|67.165.29.63

If it isn't in the database then it won't show on the data. Also remember
echolink is a constantly changing database so what you see now may not be
what you see a minute from now.

For most users echolink is a nuisance more than an asset. I have locked my
echolink down with permit lines and anyone that wants to use has to ask and
I put them in the permit= line in echolink.conf. I really wish more people
would do this as in large connected hubs if more than one person has
echolink enabled and wide open it allows anyone to come in even if a single
user had it locked down. You can use a wildcard in a permit line so

permit=wa3dsp*

would be the same as

permit=wa3dsp,wa3dsp-l,wa3dsp-r


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*



On Sun, May 28, 2017 at 4:57 PM, "Sean McCarthy via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> I guess I'd like to know if anyone else is experiencing this, or is it
> unique to my node...
>
> To recap, 99% of my echolink connections are logged like this:
>
> > Sat May 27 21:31:39 EDT 2017 == 43732 Connected EchoLink 3501912 ==>
> No-Info... EchoLink 501912
> >
> > Despite debugging at the CLI showing:
>
> >
> > -- new CALL=WX8L,ip=107.23.146.140,name=        Sean
> >
>
> So we can see the correct information is available to asterisk, but what
> gets passed to supermon / connection log is bad...
> _______________________________________________
>
> 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