[arm-allstar] Echolink Telemetry

Doug Crompton wa3dsp at gmail.com
Wed May 1 23:25:12 EDT 2019


Mike,

 There are some inconsistencies in Echolink telemetry we are looking into.
Both Allstar and Echolink have their own settings for playing
connect/disconnects or not but as far as I know they would equally effect
both Allstar and Echolink.


*73 Doug*

*WA3DSP*

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

On Wed, May 1, 2019 at 6:38 PM "Mike Besemer via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Greetings all,
>
> My primary node (48166) is connected to a link radio which links to my
> repeater at a different location.  This node also has Echolink installed
> and
> running.
>
> I'm trying to find out if it's possible to announce Echolink
> connects/disconnects on 48166 (via RF) but *NOT* announce other node
> connects/disconnects.  I have 3 other nodes in various locations that I use
> to connect to 48166  for general monitoring of the repeater, etc., and I
> don't see the need to have those connects announced over the repeater.
> Likewise, if another node connects to me I expect them to announce
> themselves, so the connect message is kind of redundant (and lengthy).
>
> I've mucked about with the telemetry settings, but haven't been able to
> accomplish what I'm trying to do.
>
> Thinking about it even more, it'd be kind of handy to be able to control
> telemetry on a by_node basis (to include Echolink), similar to the way
> courtesy tones can be controlled.  That way I could turn off the
> announcements for my nodes (which connect and disconnect frequently) but
> leave it on for other nodes.
>
> Is any of this possible now or as future enhancements?
>
> 73,
>
> Mike
> WM4B
> _______________________________________________
>
> 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