The node in question running within a Proxmox Deb12 VM and uses a RIM-Lite interface.
uname -a reports 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) x86_64 GNU/Linux and asterisk -V reports Asterisk 20.11.0+asl3-3.2.0-2.deb12
It has been running just fine for some time now and yesterday, I upgraded (apt update/upgrade). As soon as I did, the audio delivered (TX Audio) became very choppy and did so at a regular interval of (approximated) 4 or 5 Hz rate. The best description I can give is “watery sounding”.
Not super helpful, but my node is also a Proxmox VM running the same ASL3 version, and I do not have this issue. The interfacing is all VOTER (RoIP), though, no USB.
and you updated/upgraded from what version of ASL3?
and did your update/upgrade also pull in a updated kernel? I ask because if this is your first upgrade in 2025 then you may be affected by the updated kernel issue we had at the start of the year. You may want to look at the /etc/modprobe.d/asl3-snd-usb-audio.conf file and the lowlatency setting. Try changing the value from “0” to “1”, reboot, and see if that helps.
I listed the ASL version I upgraded from in the OP - Asterisk 20.11.0+asl3-3.2.0-2.deb12
And yes, kernel was updated as part of the apt upgrade.
I fell back to the previous version after the problem made itself known (How I love ProxMox backups!) but I can try upgrading again and employing your suggestions over the weekend. I’ll report back.
My hub was updated (radioless no USB) and no issues with it either. Interestingly, I have another Proxmox node (running on a different platform), also with the RIM Lite interface and it is just fine as well. Perhaps WCO’s ideas will work on the troublesome node.
My bad. I focused on “update/upgrade” and the “asl3-3” and didn’t notice that you are at “asl3-3.2” and not the latest “asl3-3.3”. Kinda surprised that your “update” didn’t pickup the packages we released on 03/18 … but maybe you did your update before Tue and are just now posting to Community.
The audio issues that followed the kernel update were unexpected (and a pain). The lowlatency option took care of the issue on most of the affected systems.