[arm-allstar] autopatch semantics
Patrick Perdue
borrisinabox at gmail.com
Sun Sep 4 13:48:08 EDT 2022
Greetings:
I have some questions about using an autopatch on HamVoIP behind another
controller.
I am working with a club who is using HamVoIP on the link port of an
Arcom RC-210, currently half duplex (trying to convince them to change
the link port to full duplex). duplex=0, linktolink=yes.
As I understand it, the autopatch uses VOX in duplex modes 0 and 1, and
there is no way to disable VOX for those modes. Is that correct?
If the link port is full duplex, and linktolink=yes, this would be a
full duplex setup, and VOX would be unnecessary.
If VOX can't be disabled, or the threshold adjusted, I would like to
impose a hangtime only while the autopatch is up, so that when long
pauses happen, it doesn't drop. This repeater has a very short hangtime.
My thought was to use althangtime or another control state to do this,
change duplex to 1 and manually disable all the courtesy tones and
unnecessary telemetry.
First, how would one dynamically change hangtime only while the
autopatch is active?
Second, is this even a reasonable idea in the first place, or is there
something better?
I thought of using duplex=3 when the port is set to full duplex on the
controller, but I think that would cause the repeater controller to not
properly send the appropriate courtesy tone as defined for each port,
since the node is still transmitting but with no audio in that mode.
Any suggestions are appreciated.
Thanks and 73
N2DYI
More information about the ARM-allstar
mailing list