I am rebroadcasting NASA Audio. It is working great. The problem is that My DMR and D-STAR will timeout on very long transmissions. I have been looking all over for away to force a 10s unkey after 3 or 5 minutes of continous keying. I Zopier doesn’t have away to adjust the VOX noise floor nor does Allstar. Is there away to make this happen? I just need an unkey if the transmission is longer than X amount. I think I might be able to make a dialplan that does this but everything I see disconnects. That is not what I am after.
The problem yesterday was that the wind was blowing over the microphones and the vox detected that and kept everything keyed. I could use a USBSoundcard to USBSoundcard but I wanted to go everything internal. Would I be better with Linux desktop then Windows? Suggestions are welcome.
Using VOX for your application is not a good choice at all as your experience indicates. However, forcing an unkey is exactly what a timeout timer does. Did you disable the TOT on your ASL node? By default it's 3m (totime=180000 which is 3m in milliseconds).
When it times out. It doesn't rekey until the signal drops. I know VOX is not the best way. But unless I want to have a bunch of hard ware from one USB to another USB. This is the only option I have found so far. even with that. If it is a long transmission. It will not rekey until the signal drops.
I had to remove the totime to get it to get going. Once it hits the totime. It stops until the signal is gone like I advised in my other reply. totime is great but it doesn’t autoreset. Which is what it is suppose to do.
Here's a PHP script that Claude helped write. I've started running it on node 516221. I've used a bash script in the past. This may, (or may not) , work. See the comments at the top of the script. You will need to add your event and set a global variable for the feed channel to be muted. You will also need to load the res_mutestream.so module.
AI has a difficult time with Allstar sometimes, because of multiple versions of Asterisk and Allstar. Assuming my 516221 node is is working better now, I guess you could connect to 516221. I may reduce the timeout a bit les than 3 minutes. Most systems should handle 3 minutes though. https://space.rfnet.link