Not sure if this is possible or not.
We have a duplex repeater node running mixed audio and two courtesy tones - one for local traffic on the repeater - another for remote (link) traffic.
When the link is active and a user is talking, it's possible to key the repeater and activate the local traffic courtesy tone. This can get annoying if people continue to button push.
Is there a way to silence a courtesy tone on link activity?
Running latest hamvoip image
Generally not without being tricky.
How to be tricky.....
Explaining it a bit backwards for better understanding.
Use [controlstates]
To change which CT you want in each 'state' profile
You can set a CT to nothing if you wish for silence.
You can also use a gpio tied to a COS with perhaps some logical inversion or buffering and using that gpio to plat a sound file for a CT where the input CT is normally blank..
There are other tricky things you can do, but if you look at this for starters, I'm sure your wheels will start turning on it.
As I understand it, you only want the local courtesy tone to not fire when there is traffic from the link, not all the time... In other words, if no one is keyed from the link side, play the tone when someone keys the repeater locally. If there is link activity, don't play the tone when the repeater is keyed locally for the duration of the remote transmission, then switch to normal behavior when the link unkeys.
I can't think of an obvious, easy way to do this. Maybe something with events and controlstates, setting up a state with a silent or undefined courtesy tone, then constantly switch states based on events defined in an events stanza for the node.
Off the top of my head... Set your remote traffic CT to something like remotect.ulaw in rpt.conf but don't actually have that file exist, and then have two real files, sound.ulaw and silence.ulaw. Use events to trigger shell commands that create/change remotect.ulaw to be a symlink to silence.ulaw whenever link rx keys, and change to sound.ulaw when it unkeys.
Thanks for all the replies and yes this is correct.
It's not really a necessity, it's just more of an annoyance when people button push over the top of link activity and you hear the roger beep on the local side.
On another note - I also have noticed that the talkoverID doesn't seem to kick in properly for link transmissions. For instance I have been listening to a conversation between two stations coming in over the link. My repeater sends an ident in morse (the ID talkover) but then it will ID in voice anyway - although usually it's audio ducking so it's not too bad.
Just quirky!