[arm-allstar] telemetry control

[David McGough]

Hi Patrick,

telemenabled=255 should get everything turned back on. You are correct 
that the "255" is part of a bitmask, allowing pieces and parts to be 
enabled/disabled.  The telemetry management code was historically one of 
the "ugliest" portions of the AllStar codebase, with features just hacked 
in here and there.  Much of this has now been re-written, the remainder is 
on the 2022 to-do list....As such, bitmask values, etc., are subject to 
change between releases, at this point. So, I'm hesitant to say much 
between either "all on" or "all off," for now.

What exact features are you missing in the 1.7+ releases?

Thanks,

73, David K4FXC




On Wed, 26 Jan 2022, "Patrick Perdue via ARM-allstar" wrote:

> Hi:
> 
> I'm being asked by multiple users on my system (at least seven so far) 
> how to restore full old telemetry support from previous versions of 
> HamVoIP. Apparently, if you have
> 
> telemenabled=255
> 
> in your node's stanza, this will provide voice telemetry only for 
> connections to your node directly, not any of the foreign links. I, 
> personally, prefer this behavior in a lot of cases, but I guess not 
> everyone does.
> 
> So, my question is, given that telemenabled=0/255, what are the other 
> options in that mask? I assume there are other partial or full switches 
> within this parameter. Does something currently exist in the codebase to 
> revert back to the old way of providing full telemetry as in versions 
> prior to HamVoIP Asterisk 1.65.xx?
> 
> Thanks and 73
> 
> N2DYI
> 
> _______________________________________________
> 
> 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/4 web page - http://hamvoip.org
>