Hi,
I'm using pjsip with JACK too, so I thought I'd share my experience.
Firstly the pjsip build of portaudio and its use by pjsua doesn't work well with multiple providers. I looked around the code and wasn't quite sure what was going on. It was impossible to get pjsip to pick the jack ports - the best I managed was to get it to pick the alsa jack device.
So I built a custom portaudio disabling alsa and oss so jack was the only option. I too had to hack the build to get it to compile and to add the -ljack parameter.
To get pjsua to play, I had to turn monitoring off using qjackctl because with monitoring on my sound card looks like its got four inputs and pjsua croaks if there are more than two channels.
I didn't have any sample rate problems once I had sorted these out.
Running two pjsua instances on the same pc now works, since each gets their own client in Jack (my main need for Jack in the first place)
But it tends to lock the machine up. I turned realtime off on jack and this helps a lot but of course now one gets xruns all over the place.
So I'm not sure the threading model in pjsip is very jack friendly - is it possible portaudio or pjsip are running too much code in the jack callback?
Julian
---------------------------------
Sent from Yahoo! Mail.
A Smarter Inbox.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080301/d98a4559/attachment-0001.html
