Hi Matthew, You may need to increase FD_SETSIZE (and rebuild PJSIP and SWIG). Regards, Ming On Thu, Jan 14, 2016 at 3:28 AM, Matthew Williams <mgwilliams at gmail.com> wrote: > I think a lot of the segfaults (as well as the other peculiar behavior I > was having with pjsua2 regarding built in functions) had to do with the > Call object leaving scope and being garbage collected. > > I now have a test app that is running on python3-pjsua2, but after 300 > calls or so it also throws the "PJ_ETOOBIG" error just as the old bindings > did. > > 01:13:49.640 pjsua_media.c !..Unable to create media transport: Size is > too big (PJ_ETOOBIG) [status=70017] > 01:13:49.640 pjsua_media.c ..Error creating media transport: Size is too > big (PJ_ETOOBIG) > 01:13:49.640 pjsua_call.c .Error initializing media channel: Size is > too big (PJ_ETOOBIG) [status=70017] > 01:13:49.640 call.cpp pjsua_call_make_call(acc.getId(), > &pj_dst_uri, param.p_opt, this, param.p_msg_data, &id) error: Size is too > big (PJ_ETOOBIG) (status=70017) [../src/pjsua2/call.cpp:485] > > My test app is using asyncio on Python 3.5, so it may be slightly harder > to follow than is necessary, but here are the steps to reproduce: > > 1. I built Python 3.5 bindings from latest trunk of pjsip (diff for pjsip: > https://gist.github.com/mgwilliams/85085cd9e0654e43358e) > 2. I ran "sipp -sn uas -p 5060" in one shell > 3. In another shell I ran my test app ( > https://gist.github.com/mgwilliams/6f1af047b76b93edfb1b) > > > > > On Tue, Jan 12, 2016 at 3:36 PM, Diogo Paschoal <paschoalete at gmail.com> > wrote: > >> Hi, Matthew. >> I'm using Python Bindings too. >> I'm having the same segmentation fault problems as you. This looks >> random and i don't know how to solve it. >> Did you succeeded in any way to use it fully functional? >> I'm trying to create a CAP (Call Analysis Progress) script to know when >> a human, a vox mail box get the call or if is a disconnected number using >> SIT (https://en.wikipedia.org/wiki/Special_information_tones). Do you >> have any glues? >> >> Thanks. >> >> >> >> Em 11/01/2016 20:19, Matthew Williams escreveu: >> >> Apologies for the monologue. The CANCEL was being triggered by the Call >> object leaving scope. I slightly re-arranged the code and now it's working >> as expected. >> >> On Mon, Jan 11, 2016 at 6:01 PM, Matthew Williams < >> <mgwilliams at gmail.com>mgwilliams at gmail.com> wrote: >> >>> I did some more experimentation with pjsua2 and python. This app ( >>> https://gist.github.com/mgwilliams/bd02cd294a2b8347c649) is running >>> fine, but pjsua transmits a CANCEL immediately after receiving the 180. >>> >>> On Mon, Jan 11, 2016 at 7:56 AM, Matthew Williams < >>> <mgwilliams at gmail.com>mgwilliams at gmail.com> wrote: >>> >>>> I am using the trunk version of PJSIP. >>>> >>>> On Sun, Jan 10, 2016 at 9:51 PM, Nanang Izzuddin <nanang at pjsip.org> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> Yes, generally Call (Python) object should remain valid during an >>>>> active call, but perhaps this is not the case, so could you clarify a bit >>>>> more about 'destroying a call' and more detail about the problem (e.g: >>>>> sample scenario, pjsip version, which API or Python binding you are using) >>>>> would be useful. >>>>> >>>>> Btw, in case you are still using the pjsua Python >>>>> <https://trac.pjsip.org/repos/wiki/Python_SIP_Tutorial> module (in >>>>> pjsip-apps/src/python), just FYI, it is about to be deprecated and replaced >>>>> by the new pjsua2 API >>>>> <http://www.pjsip.org/docs/book-latest/html/index.html> that has >>>>> Python binding via SWIG. >>>>> >>>>> BR, >>>>> nanang >>>>> >>>>> >>>>> On Fri, Jan 8, 2016 at 11:24 PM, Matthew Williams < >>>>> <mgwilliams at gmail.com>mgwilliams at gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm using the Python bindings (updated for Python 3.5), but it seems >>>>>> calls are not being destroyed. I've dug around, but do not see any way to >>>>>> destroy a call other than calling hangup(). Am I missing something? >>>>>> >>>>>> Thanks! >>>>>> >>>>>> _______________________________________________ >>>>>> Visit our blog: <http://blog.pjsip.org>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>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 listpjsip at lists.pjsip.orghttp://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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20160118/77ea4b8b/attachment.html>
