[arm-allstar] Telemetry Request

[Doug Crompton]

Unfortunately the telemetry system in Allstar is rather crude and a kludge
that really needs attention. It is on our list but one of those things
where a more complete rather than a patch overhaul is required. The
telemdefault=2 which is the default in the hamvoip code is right now timed
at two minutes to muting. As a temporary fix we will be adding an rpt.conf
parameter that allows you to adjust the mute time. A more realistic value
would be 15 or 20 seconds allowing you to hear your own telemetry but
muting promptly.

The connect/disconnect telemetry is global meaning on a large network of
nodes it is sent to all of them. The control of whether you hear it or not
is at each individual node. One problem we recently saw is that if any node
is misconfiguration within a connected network it can send bogus telemetry
info to all the nodes. One case we just found was a constant string of
"already in this mode" and other strange telemetry messages. When this
happens and you have telemetry turned on it can be very annoying.

For now there are several things you can do. Use telemdefault=0  - for no
telemetry or telemdefault=2 with a short mute time once we release the
parameter for now 2 minutes. You also have the option of greatly reducing
the volume of telemetry in general and even more when a node is
transmitting.

.; Audio Level settings in dB

telemnomdb=-9
                                ; Overall reduction in telemetry level
telemduckdb=-15
                                ; Telemetry level reduction with signal

telemnomdb  is the general level of telemetry vs. voice  level. Shown here
as a -9db reduction

telemduckdb is the amount of reduction when a voice signal is present.

You can set these values considerably lower (higher minus value) to reduce
the telemetry levels to your liking.

Hopefully over time we can make more improvement in the Hamvoip telemetry
system.


*73 Doug*

*WA3DSP*

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


On Sun, Jul 14, 2019 at 8:49 AM "M Lech via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hi Doug,
>
> A while back I'd inquired of adding an option to the telemetry settings. To
> reiterate in short, we'd be thrilled to have a third Telemetry option. It
> would send only Function Complete (beep-beep) for any Connect or
> Disconnect. Right now, we run our RTCM hub with telemetry set as 2 ("Only
> your telemetry actions, then mutes in 1 minute"). With telemetry = 1, we
> were bombarded by connect and disconnect verbosity. All we want are simple
> beeps to tell us when someone connects or disconnects. We can easily check
> Supermon for more details as needed. Right now, we don't hear anything when
> someone connects and we'd like some indication so we don't seem to ignore
> them. This would really help.
>
> Is there a way I'm missing where this could be done without modifying the
> actual distro? If so, I'm all ears. Thanks guys!
>
> 73,
> Matt W6KGB
> GRONK Radio
> _______________________________________________
>
> 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
>