On Wed, Aug 6, 2008 at 6:44 PM, Benny Prijono <bennylp at pjsip.org> wrote: > On Wed, Aug 6, 2008 at 10:26 AM, Alberto Takeshi Mayama > <mayama at brastel.co.jp> wrote: >> >> Hello, >> I've written a small app to test calls, simulating 2 terminal using pjsua. >> Since I don't care about audio (I test RTP sending DTMF), I'm calling >> pjsua_set_null_snd_dev immediately after pjsua_init to disable audio >> hardware allocation. >> The app works fine in most of the machines I have tested, but in some >> of them, pjsua logs this: >> >> *** PULSEAUDIO: Unable to connect: Connection refused >> *** PULSEAUDIO: Unable to connect: Connection refused >> *** PULSEAUDIO: Unable to connect: Connection refused >> *** PULSEAUDIO: Unable to connect: Connection refused >> >> This doesn't prevent the app to work, but the above takes 40 seconds >> to complete, so it's really annoying. >> This may be a hardware configuration problem in the machine, but since >> we instructed pjsua not bind to audio devices, I suppose this is a >> pjsua bug. >> > > I suspect that happens during sound device subsystem initialization. > Although you call pjsua_set_null_snd_dev(), internally pjmedia would still > initialize the sound device subsystem so that later application can switch > to using a real device if it wants to. This initialization routine does not > open the devices, but rather just to initialize the underlying driver to get > the list of devices. And I think this is where it gets stucked. > > If you really want pjmedia to stop touching the sound device, use > "--disable-sound" when running configure, or put this in your config_site.h: > > #define PJMEDIA_SOUND_IMPLEMENTATION PJMEDIA_SOUND_NULL_SOUND > Hi Benny, thanks, adding the define solved it. Regards, takeshi > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >
