I am running on Archlinux (technically Parabola linux). Every time that
a call ends, the pjsip logging stops with the following line:
pjsua_aud.c .Closing pulse sound playback device and pulse sound
capture device
And the only thing I can seem to do is control+C.
This is observable in the "simple_pjsua.c" sample application as well as
in the pjusa application.
Is this something other people have experienced?
Or is there something I can do to either fix this problem or
troubleshoot further?
Thanks,
Ryan
I have the same behaviour with two different machines. Specifically when I hang up calls it freezes while releasing audio. This happens with every call. The first time I hit enter in the frozen terminal it outputs '>>>>'. Remaining times I get new lines but nothing else.
This occurs when building from both the 2.7.2 and 2.8 release tarballs.
I have tried two different computers both have this issue.
On a netbook running arch linux:
default audio device is PulseAudio displays 'Closing pulse sound playback device and pulse sound capture device' before freezing
Ubuntu 16.04 64bit vm on a 64bit windows host:
default audio device is Intel 82801AA-ICH displays 'Closing default sound playback device and default sound capture device' before freezing
additionally pauses during startup (between 'Module mod-invite' registered and ALSA driver found 16 devices) for 20 seconds.
Noting the freeze doesn't occur when using Null audio.
-----Original Message-----
From: Ryan Beethe [mailto:ryan@splintermail.com]
Sent: Monday, 8 October 2018 3:56 p.m.
To: pjsip@lists.pjsip.org
Subject: [pjsip] Freeze on pulse sound device
I am running on Archlinux (technically Parabola linux). Every time that a call ends, the pjsip logging stops with the following line:
pjsua_aud.c .Closing pulse sound playback device and pulse sound
capture device
And the only thing I can seem to do is control+C.
This is observable in the "simple_pjsua.c" sample application as well as in the pjusa application.
Is this something other people have experienced?
Or is there something I can do to either fix this problem or troubleshoot further?
Thanks,
Ryan
Visit our blog: http://blog.pjsip.org
pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org