Ah sorry, Olle sent me a log file with Address Incomplete error and I thought that was the one that you're testing with. Anyway, I tested the same configuration but with --null-audio on both instances (since I don't have sound card in my colinux), and as expected, it didn't freeze. Was it really freezing, or the SIP worker thread is not responding? If the whole application was freezing, that's strange, since the console UI is in another thread so even if the worker thread gets blocked for some reason the console UI should still be running. This especially true for callee (and instance 2 in your setup is callee), unlike caller where the console UI thread is responsible for creating the call (so if make_call() gets stucked, the console UI will get stucked too). Can you share any logs maybe? cheers, -benny On 2/28/08, Dan <dan.aberg at keystream.se> wrote: > Actually I'm not registering with OpenSER or any other server. I just > run pjsua without configuration file and the parameters in my originally > post. > Anyway the second pjsua instance freezes, I don't think it should do > that, strict route or not :) > > > /Dan > > > On Thu, 2008-02-28 at 15:36 +0000, Benny Prijono wrote: > > On 2/28/08, Dan <dan.aberg at keystream.se> wrote: > > > Hi, > > > I just checked out the latest revision(1824), and now I'm not able to > > > make a call between two instances running on the sam host. > > > > > > Instance 1: > > > ./pjsua-i686-pc-linux-gnu --local-port=6028 --no-vad --ec-tail=0 > > > --auto-answer=200 > > > > > > Instance 2: > > > ./pjsua-i686-pc-linux-gnu --auto-loop --no-vad --ec-tail=0 > > > --auto-answer=200 --null-audio > > > > > > When I make a call from instance 1 to sip:127.0.0.1, instance 2 freezes > > > after receiving the initial INVITE. > > > > > > The last time I tried this was with revision 1786, which worked just > > > fine. > > > > Hi Dan, > > > > >From the log (off list), it seems that the call was rejected with 484 > > Address Incomplete, because the request was like this: > > > > INVITE sip:domain SIP/2.0 > > Route: <sip:400 at domain> > > > > So you're using strict route, and it seems that your OpenSER couldn't > > handle this (maybe a configuration problem?). > > > > This worked in r1786, because we had this bug: > > http://trac.pjsip.org/repos/ticket/492, which incorrectly swapped back > > the Route with the request URI after the request is challenged with > > 401/407. > > > > So the solution is to use loose route, by adding ";lr" in your route URI. > > > > cheers, > > -benny > > > > > > > Thanks, > > > Dan > > > > > > > > > > > > _______________________________________________ > > > 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 > > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > 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 >
