Looks like your problem isn't pjsip related but SIP related. If your 30 seconds are actually exactly 32 seconds, then I'm correct. Try to make your scenario work with CSIPSimple (based on pjsip) on Android. Setup on it your SIP credentials, place the call and see if it works. If it does, then you have a problem with your code, if it doesn't, then you have a problem with your SIP server. On Thu, Jan 14, 2016 at 3:57 PM, Matthew Williams <mgwilliams at gmail.com> wrote: > Is there anyone on this list with an in-depth understanding of the entire > stack that would be interested in doing some paid consulting? > > I have made considerable progress in getting an app running using the > swig/python bindings for pjsua2. However, due to the limited documentation, > it is slow going -- for example, it took quite some time to track down the > cause of segfaults to the Call object being lost from focus. > > My current issue is related to calls that are cancelled. It appears that > if hangup is called prior to the call entering the confirmed state, the > disconnected state is only entered some 30 seconds later. Since I am > writing a server application, this quickly eats up call limits. > > Please feel free to reply privately. > > Thanks! > > _______________________________________________ > 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 > > -- Carlos http://caruizdiaz.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20160114/8def4634/attachment.html>
