Many thanks all four your advices. I start jackd in promisuous mode. I created a Unix group named 'jack-access', with all participants for the task (including the asterisk user) I set  JACK_PROMISCUOUS_SERVER=jack-access  everywhere (including within the systemd script for asterisk) I can check that this environment variable is really set via   /proc/<asterisk pid>/environ All participants are able to execute  jack_mixer So all participants are able to reach the jackd server. Unfortunately I still have errors when I place a call to this asterisk channel:     ../..     -- Executing [6000@default:5] JACK("SIP/6007-00000003", "") in new stack [May 10 13:34:25] NOTICE[2899][C-00000003]: app_jack.c:192 log_jack_status: Client Open Status: Failure, Server Error   == Spawn extension (default, 6000, 5) exited non-zero on 'SIP/6007-00000003'   ../.. How can I get more log messages from the jackd server? Best regards Christophe

Le 11/05/2018 à 17:26, Chris Caudle a écrit : After a system reboot, I get some advances. (systemd includes too much sorcery for me) Now I can execute jack_evmon in another terminal and see activity of the jackd server: $ jack_evmon Graph reordered Client SIP/6007-00000000 registered Graph reordered Graph reordered Port 5 registered Port 6 registered Graph reordered Graph reordered Port 5 unregistered Port 6 unregistered Graph reordered Client SIP/6007-00000000 unregistered Graph reordered Unfortunately there are still (other) errors in the asterisk console:     -- Executing [6000@default:5] JACK("SIP/6007-00000000", "") in new stack [May 11 20:30:00] WARNING[30222][C-00000000]: app_jack.c:600 queue_voice_frame: Tried to write 3844 bytes to the ringbuffer, but only wrote 1679 [May 11 20:30:00] WARNING[30222][C-00000000]: app_jack.c:600 queue_voice_frame: Tried to write 3844 bytes to the ringbuffer, but only wrote 0 [May 11 20:30:00] WARNING[30222][C-00000000]: app_jack.c:600 queue_voice_frame: Tried to write 3844 bytes to the ringbuffer, but only wrote 0 ../.. [May 11 20:30:10] WARNING[30222][C-00000000]: app_jack.c:600 queue_voice_frame: Tried to write 3844 bytes to the ringbuffer, but only wrote 0     -- Unregistered SIP '6007' Indeed, I have no audio in the phone. There are probably other issues elsewhere in my system... The adventure goes on! Best regards Christophe

On Fri, May 11, 2018 3:59 pm, Chris Caudle wrote: OK, I had time to search a little. That function is from jack, not asterisk, but I think the asterisk code may not be using it correctly. The jack ringbuffer.h file has this note: return the number of bytes write, which may range from 0 to cnt So it seems that the write() function is documented as possibly writing less than the full data given. There is also this function, which seems to be for getting the amount of free space available in the ringbuffer, but I cannot see that the asterisk code ever calls this function: /** * Return the number of bytes available for writing. * * @param rb a pointer to the ringbuffer structure. * * @return the amount of free space (in bytes) available for writing. */ size_t jack_ringbuffer_write_space(const jack_ringbuffer_t *rb); In short, I think this is a bug in the asterisk implementation. It should be checking how much free space is available and only attempting to write that, or should just deal with write() not writing the full amount of data and calling write() again later to finish writing all the data. -- Chris C

On Fri, May 11, 2018 23:41, Christophe Lohr wrote: This is just a warning. If you'd check the available size before writing the result would be the same. Why the ringbuffer has not enough write space can have several reasons from logic errors to random other reasons. However you could simply enlarge the ringbuffer capacity and see if the warning still appears. in app_jack.c: /* The number of frames the ringbuffers can store. The actual size is RINGBUFFER_FRAME_CAPACITY * jack_data->frame_datalen */ #define RINGBUFFER_FRAME_CAPACITY 100 set this to 1000 just for a test and re-compile. Greetings Thomas

Am Donnerstag, den 10.05.2018, 15:50 +0200 schrieb Christophe Lohr: Long time ago I was using Jack2 as a system-wide service on HTPC running Ubuntu using following upstart script //// start on runlevel [2345] or local-filesystems stop on runlevel [!2345] emits audio-bus console log env HOME=/root pre-start script if [ ! -f /run/dbus/.env ]; then eval `dbus-launch --auto-syntax` echo "export DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID" > /run/dbus/.env echo "export DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS" >> /run/dbus/.env chmod 600 /run/dbus/.env fi end script post-start script . /run/dbus/.env jack_control start if [ -f /etc/default/jackd ]; then awk '/^[esdri]/{system("jack_control "$0)}' /etc/default/jackd awk '/^ /{system("jack_load "$0)}' /etc/default/jackd awk '/^>/{ system("jack_connect "$2":capture_1 "$3":playback_1"); system("jack_connect "$2":capture_2 "$3":playback_2"); }' /etc/default/jackd fi end script post-stop script . /run/dbus/.env if [ -f /etc/default/jackd ]; then awk '/^ /{system("jack_unload "$1)}' /etc/default/jackd fi jack_control exit end script \\\\ upstart is now a history but the principle should be the same I guess. systemd allows you even to have user-level session initiation, so should be much mroe flexible in this regard. The key point back then was /run/dbus/.env - that one allowed me to join same DBus session where JackDBus was spawned. Then each application which was going to use Jack should be started with .env file loaded populating the environment variables. You can ignore /etc/default/jackd - that one was my custom recipe file which pre-loaded required modules and made required connections at the early start.