Hey Benny! So 2 pjsua clients from the latest SVN trunk registering and calling through OpenSER 1.3.1-notls. Their config is same: --id=sip:tcp-user at example.com;transport=TCP --registrar=sip:example.com:50605;transport=TCP --max-calls=1 --auto-answer=180 I am registerting to port 50605 to get rid of ALG rewriting my IP addresses. On the first client after sending 180, these are last logs: TRACE: 08:36:49.825 tsx0x81dc3ec State changed from Proceeding to Proceeding, event=TX_MSG TRACE: 08:36:49.825 dlg0x81e4924 Transaction tsx0x81dc3ec state changed to Proceeding Segmentation fault On second client after receiving 180, these are last logs: TRACE: 08:36:51.927 tsx0x821c28c Incoming Response msg 180/INVITE/cseq=9964 (rdata0x81d328c) in state Proceeding TRACE: 08:36:51.927 tsx0x821c28c State changed from Proceeding to Proceeding, event=RX_MSG TRACE: 08:36:51.927 dlg0x82172ec Received Response msg 180/INVITE/cseq=9964 (rdata0x81d328c) TRACE: 08:36:51.927 dlg0x82172ec Route-set updated TRACE: 08:36:51.927 dlg0x82172ec Transaction tsx0x821c28c state changed to Proceeding Segmentation fault As I've said before, if I send 200 directly after 100 then it works fine. Just 180 which has before changed call state to EARLY makes it segfault. During writing of this email I realised it doesn't need to be connected to TCP and it is not! The same happens with UDP now as well. It used to work about 30 revisions back with UDP but it segfaults now. You should be able to reproduce this easily. Cheers, Ondrej On Fri, Aug 1, 2008 at 22:41, Benny Prijono <bennylp at pjsip.org> wrote: > On Fri, Aug 1, 2008 at 8:35 PM, Ondrej Sterbak <sterbo at email.cz> wrote: >> >> Hi Benny, >> >> when I make a call between 2 pjsuas using TCP transport they both >> segfault on 180 response. When I don't send 180 but 200 directly then >> it works fine. >> >> Let me know if you need some more details or logs. >> > > Yes please. > > -benny > > > _______________________________________________ > 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 > >
