Lesley Pervis wrote
Sorry for the spam, but I thought I'd mention that I can aplay no problem from the command line as the 'freeswitch' user, and yet when FS is running as that user, no luck.
Exactly seven years after your last post here, I'm there to ask if you finally succeeded to resolve the issue? My case: 1. Pi-4 with Raspbian buster und latest related FreeSwitch distribution, apt-upgraded and updated just yesterday 2. aplay is working both with the audio jack and with bluetooth (although not simultaneously: as soon as I have a bluetooth audio connection, the audio jack stops to work, and I cannot switch back to it with "amixer cset numid=3 1", but aplay can continue to use the bluetooth connection again after I issue "amixer cset numid=3 65536") 3. it seems that I do not have any permission issue as both pi and freeswitch are in the audio group and related devices under /dev/snd are in that group 4. I have already installed alsaoss, libasound2 and libasound2-dev 5. The output of "pa rescan" in fs_cli is the following: 2020-06-19 06:55:18.803478 [INFO] mod_portaudio.c:3186 Looking for new devices. 2020-06-19 06:55:18.803478 [INFO] mod_portaudio.c:2102 PortAudio version number = 1246720 PortAudio version text = 'PortAudio V19.6.0-devel, revision 396fe4b6699ae929d3a685b3ef8a7e97396139a4' 2020-06-19 06:55:18.943433 [DEBUG] mod_portaudio.c:1773 global indev [-1] 2020-06-19 06:55:18.943433 [ERR] mod_portaudio.c:1777 Cannot find an input device 2020-06-19 06:55:18.943433 [DEBUG] mod_portaudio.c:1786 global outdev [-1] 2020-06-19 06:55:18.943433 [ERR] mod_portaudio.c:1790 Cannot find an output device 2020-06-19 06:55:18.943433 [INFO] mod_portaudio.c:2125 Number of devices = 0 Any clue, what could be wrong on my side? Thanks! -- Sent from: http://freeswitch-users.2379917.n2.nabble.com/