[arm-allstar] Enable and disable node connections

[Patrick Perdue]

AFAIK, you, as the end-user, can't change that announcement. It's 
compiled directly into app.rpt.

Think of it this way.

The function, which disables incoming connections, is active. If the "no 
incoming connections" function is enabled, incoming connections won't 
happen. Thus, NOICE makes sense in that context, because no incoming 
connections is enabled. Yes, this means incoming connections are 
disabled, but the point here is that the "no incoming connections" flag 
is true.

You now want to disable the no incoming connections function to allow 
connections again. Thus, NOICD. The "no incoming connections" flag is 
false, meaning incoming connections are allowed to happen.

It's not even a double negative if you consider exactly what it does. 
Sure, it's weird, but it isn't technically wrong.

This is probably just very old legacy stuff from the original 
Allstarlink days.


On 6/19/2022 3:15 PM, "Dave Petrie via ARM-allstar" wrote:
> Can anyone point in the direction to change the voice/telemetry
> announcements
> for the cop,49 and cop,50 commands.
> As they are they don't make sense to me and I want to reverse them.
> issuing cop,49 Disable Incoming Connections the announcement says
> N O I C E which in my mind means node incoming connections enabled
> but it disables incoming connections.
> issuing cop,50 command the announcement says N O I C D
> this enables the incoming connections but my minds hears, node
> incoming connections disabled.
>
> cop,49 ; Disable Incoming Connections (Control State noice)
> cop,50 ; Enable Incoming Connections (Control State noicd)
> _______________________________________________
>
> 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