439.575 MHz is a link/control frequency, and ALRC typically does not publicly publish those. They are resident between 435-440 MHz. Most 70 cm repeater outputs are above 440.0 MHz.
Under Links, these show as public items. There is a need to suppress the publishing of control, auxiliary, and backbone links. Typically, in the case of mischief, these links are used to send the commands to the repeater to turn off the transmitter.
It may be as simple as defining the standard split in a given band, and if the split exceeds that, add a check box for "Publish Link/Repeater publicly."
Steps to reproduce the behavior
See above.
Clear description of what you expected to happen
Tag/field/database column needed to suppress publishing of some objects. In the Repeater Update view, under Links, this should be a check box for "public publicly."
Additional information
Provided above.
Links are typically determined as horizontal polarization, however some or many are implemented as vertical polarization. Cross polarization is best, but some hams use non-directional antennas anyway (despite recommendations and coordinations for directional antennas). Link frequencies are reused, and CTCSS (if in use) should be different from adjacent links.
Ideally, a link should be a combination squelch + repeater CTCSS, but the controller logic doesn't exist right now to support remote TX hang while RX noise is transmitted after detect of a valid repeater PL on the remote RX. This way, the voter doesn't switch inputs and tone decoding can be used to shut down individual local RX when the CTCSS goes away (or reverse burst / CG happens).
Description of the bug
In https://al.repeatercouncil.org/repeaters/?q=&p=31&dc=False&o=OutputFrequency
439.575 MHz is a link/control frequency, and ALRC typically does not publicly publish those. They are resident between 435-440 MHz. Most 70 cm repeater outputs are above 440.0 MHz.
Likewise the KB4CRG cross-band items:
https://al.repeatercouncil.org/repeaters/?q=&p=23&dc=False&o=OutputFrequency
Under Links, these show as public items. There is a need to suppress the publishing of control, auxiliary, and backbone links. Typically, in the case of mischief, these links are used to send the commands to the repeater to turn off the transmitter.
It may be as simple as defining the standard split in a given band, and if the split exceeds that, add a check box for "Publish Link/Repeater publicly."
Steps to reproduce the behavior See above.
Clear description of what you expected to happen Tag/field/database column needed to suppress publishing of some objects. In the Repeater Update view, under Links, this should be a check box for "public publicly."
Additional information Provided above.
Links are typically determined as horizontal polarization, however some or many are implemented as vertical polarization. Cross polarization is best, but some hams use non-directional antennas anyway (despite recommendations and coordinations for directional antennas). Link frequencies are reused, and CTCSS (if in use) should be different from adjacent links.
Ideally, a link should be a combination squelch + repeater CTCSS, but the controller logic doesn't exist right now to support remote TX hang while RX noise is transmitted after detect of a valid repeater PL on the remote RX. This way, the voter doesn't switch inputs and tone decoding can be used to shut down individual local RX when the CTCSS goes away (or reverse burst / CG happens).