Both types of USB channel driver have been massively overhauled and improved with ASL3. I would suggest upgrading to ASL3 to see if your issues are resolved.
One thing in the original post stood out to me. James writes âthere are audible tones and connectsâ. Iâm unsure where the audible tones are being heard, but if Allstar-connected stations are hearing DTMF tones, that indicates that Allstar is not detecting DTMF. Allstar will mute detected DTMF tones, and will only allow the tones to be carried across Allstar if you configure propagate_dtmf=yes
Easiest thing you can try is a different HT, see if DTMF tones are muted by Allstar. I suggest monitoring the CLI while pressing DTMF tones, debug level 3 should be fine. Sometimes a single row of keys isnât detected correctly, while the rest of the keys detect correctly. Audio level is also a factor in successful decoding, as a rule, less is more, as distorted tones are tough to decode.
If you are having DTMF issues with multiple user radios, look into the RADIO_RELAX flag. Not sure whether Hamvoip compiled with or without the RADIO_RELAX flag, but I am quite certain that you wonât get access to the Hamvoip source to recomplile.
Lastly, make sure your CTCSS line is configured in simpleusb.conf to match your URI connection details. I believe URI has a special CTCSS line but have never used one. Iâm guessing this is not it as you mentioned that the node works besides DTMF. That would suggest that CTCSS / COS is configured correctly but might help to monitor those in the CLI while pressing DTMF. If using CTCSS line in Allstar, youâd need COS, CTCSS and DTMF all true for Allstar to be able to decode DTMF.
Good luck. 73
Kyle
K0KN
Thank you all for your helpful comments. As it turns out, the problem was with the RC-210 controller. The PTT function failed and thus had to be returned for repair. Also, many thanks to Ken at Arcom.
1 Like