Thanks Jeanette. But it seems that the daemon is bypassing Alsa altogether and connecting to the built in card directly, if that's possible. I must admit that Alsa/OSS/interfaces in general always tie my head in knots. Em 01/04/2020 07:10, Jeanette C. escreveu:

Hi, thanks, it's the "linphone-daemon" of Linphone 4.1.1 which registers with an Asterisk server on the same machine. The Linphone desktop app itself does access the PulseAudio sink in Jack with no problems. However I'm needing to use the linphone-daemon to which I'm sending commands with shell scripts via a Unix socket. I'm running the daemon with a configuration file, eg. linphone-daemon --config .linphonerc --pipe linphone.soc It's reading the config, although it seems to ignore the part which should specify the cards used for playback, capture and ring tone. I should add that I've found no documentation for linphone-daemon other than its help file and I'm using the config format for the preferences file of earlier versions of Linphone. Version 4.1.1 seems to save its preferences in binary, at least I've not found a text, with a good deal of searhcing. I wrote a day ago to the linphone developers list about this. Until now I've received no reply. I suspect that audio device selection is not implemented in the daemon and in which case, I'd like to try some sort of bridging to get the audio into Jack (i need to run both the phone daemon and SuperCollider though the same sound card and SC only runs with Jack) Here's the relevant part of the config: [sound] playback_dev_id=2 ringer_dev_id=2 capture_dev_id=3 echocancellation=1 mic_gain_db=0.000000 remote_ring=/usr/share/sounds/linphone/ringback.wav playback_gain_db=0.000000 local_ring=/usr/share/sounds/linphone/rings/orig.wav I built the linphone apps from this source: https://gitlab.linphone.org/BC/public/liblinphone Em 01/04/2020 10:50, Chris Caudle escreveu:

On Wed, April 1, 2020 9:24 am, Iain Mott wrote: The description of the architecture on the linphone.org web page seems to indicate that a component named Mediastreamer2 is responsible for interfacing to the audio hardware. That component has both ALSA and PulseAudio configuration options listed, but the documentation tab on the web page for that component simply says "Please refer to public header files for Mediastreamer2 documentation." The source repository is here: https://github.com/BelledonneCommunications/mediastreamer2 I looked at the Fedora package for mediastreamer2 and there was no configuration file, so presumably whatever upper layer is using that library should send the configuration it wants to use. Yes, the documentation does not seem very complete just based on a quick look at the project web page. Ouch, binary config files make any kind of debug a lot more difficult. You may have to resort to looking for the config file parsing in the source code to see if you can determine how that section of the config file is used. -- Chris Caudle