[arm-allstar] Echolink Call status on LSNODEs page versus call indication on CLI client screen

Tom Whiteside tomw at ecpi.com
Tue May 9 14:30:07 EST 2017


Thanks.   We mostly get local folks traveling outside our repeater range
coming in on Echolink but occasionally others.   I'll tell folks to not
sweat what they see on LSNODES for Echolink stations...  

73 Tom N5TW

-----Original Message-----
>Date: Mon, 8 May 2017 13:05:23 -0400
>From: Doug Crompton <wa3dsp at gmail.com>
>
>Tom,
>
>  The lsnodes data is derived from the Allstar database. The system only
updates that data once a day early in the morning on 24/7 systems or at
boot. You can force an update by running astdb.php. > So if a node changes
info it will not show up until a reboot, daily run. or forced run of
astdb.php. The reason it is done this way is so that database is not
constantly hammered.  That is for Allstar 
> nodes. I don't pay much attention to Echolink since we are an Allstar
system. It is included as a convenience but info from it is not always
accurate. Strictly my opinion but I think we should >encourage users of
Echolink, IRLP, etc that connect to Allstar on a regular basis to come over
to our side as much as possible.
>
>I run a hun with many allstar nodes and very occasionally Echolink logins
maybe because I don't advertise the echolink beyond it being on the Echolink
list so I don't often see this. That being side I >will try to look into why
that is not showing up.
>
>*73 Doug*
>
>*WA3DSP*
>
>*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*



More information about the arm-allstar mailing list