My issue is that on a reboot, the devstr for my device keeps changing . When I first set the node up the sound device read like this “3-2:1.0 → 0d8c:0012 C-Media Electronics Inc.” this is with running the command asl-find-sound. Upon a reboot, I had no sound, ran asl-find-sound and go this output “4-2:1.0 → 0d8c:0012 C-Media Electronics Inc.” I went into /etc/asterisk/simpleusb.conf and changed the devstring line to devstr = 4-2:1.0. I’m using an Allscan UCI 120 USB Communications Interface on this node. What do I need to do to keep from having to edit the devstr line in /etc/asterisk/simpleusb.conf almost everytime I reboot?
Are you using a USB hub?
If so, I would first suggest you plug it directly into a hubless port.
Make sure your asl3 software is up to date.
No USB hub is being used, it’s plugged directly into one of the usb ports on the back of a Dell Wyse 5070 computer. ASL software is up to date being that this node was just built on 11/9/2024. I also had this same issue using a Pi 5.
Can you say what else you may have plugged in USB wise ?
If you do, I might suguest a test of not plugging them in. Just the sound FOB.
Perhaps one of the dev’s who was working on this will chime in.
But it actually sounds like the device is not IDing the same all the time when queried at boot.(each time it is seen as a new device) But I don’t know that.
Nothing is plugged into the USB ports except for the sound interface.
This is, unfortunately, a known bizarre interaction between the Dell/Wyse 5070 hardware and the Linux kernel. There are USB root hubs on that device and they don’t always initialize in the same order. When the system reboots, it’s a coin-flip which one becomes “3” and which becomes “4”. I don’t recall there ever being a solution to make that behave in a sane way.
N8EI, I’m having this same issue with a Pi 5. Same sound interface.
Now that would be unexpected. Do you have a different audio adapter to rule that one out as acting oddly?