Looked at it. Also have a support case set up with Apple. The app is behaving in an orderly manner. At no well determined point PJSIP starts doing its UDP thing and it crashes. We follow Apple's advice and have a 600 sec keep alive that does nothing more than register. It does this in a background task as per Apple. No incoming traffic so its hard to figure out why PJSIP seems to "freak out" in this way. Looks like my only course is to update to 2.0 and hope the problem is handled there. BTW, when iOS sends us a reachability change notification, all we do is post another REGISTER to the server. No manual manipulation of the transport at all. On Thu, Jun 28, 2012 at 11:02 PM, Ming <ming at teluu.com> wrote: > Hi Tom, > > Please take a look at this ticket regarding the problem: > http://trac.pjsip.org/repos/ticket/1482 > > Regards, > Ming > > On Fri, Jun 29, 2012 at 10:57 AM, Tom Merriewether > <tmerriewether at star2star.com> wrote: > > What happens though is that after running for a few hours in the > background > > the messages come fast and furiously and then the app is killed by a "too > > many wake ups" fault. I'll attach a text log of what is going on. This > > seems to happen spontaneously. The log is long but if you scroll down to > > the end you can see what I am saying. It appears to work some of the > time > > but then gets lost in the weeds later. > > > > I inherited version 1.10 and have been hesitant to move to 2.0. I tried > a > > simpleminded approach. I built the libraries for 2.0 and just swapped > the > > new libs for the old. Crashed on startup. So if I move to 2.0 is there > > some sort of a guide for changed API 1.X --> 2.0? I am a PJSIP newcomer > and > > just plowing into this is a bit intimidating, but I see your point. > > > > > > > > On Thu, Jun 28, 2012 at 7:03 PM, Benny Prijono <bennylp at teluu.com> > wrote: > >> > >> On Thu, Jun 28, 2012 at 9:04 PM, Tom Merriewether > >> <tmerriewether at star2star.com> wrote: > >>> > >>> I am running PJSIP over a TCP proxy on the iPhone. > >>> My app is getting killed with SBUnsuspendLimit exceeded 15 wakes in 300 > >>> seconds. I am about to file a bug report with Apple because I see no > >>> evidence of this in my application's log (where we capture all PSJIP > >>> messages at logging level 5). The application most recently crashed > in the > >>> background after a flurry of these PJSIP messages: > >>> > >>> PLOG --> 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: > >>> 18:38:51.872 ioq_select UDP has been replaced successfully! > >>> > >>> PLOG --> 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: > >>> 18:38:51.872 ioq_select Attempting to replace UDP socket 45 > >>> > >>> PLOG --> 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: > >>> 18:38:51.872 ioq_select UDP has been replaced successfully! > >>> > >>> PLOG --> 2012-06-27 18:38:51.873 Star2Star[158:7303] SIP PJSIP message: > >>> 18:38:51.873 ioq_select Attempting to replace UDP socket 46 > >>> > >>> PLOG --> 2012-06-27 18:38:51.873 Star2Star[158:7303] SIP PJSIP message: > >>> 18:38:51.873 ioq_select UDP has been replaced successfully! > >>> > >>> I'm not reading this as a flurry of incoming packets on the SIP > signaling > >>> socket, but since I don't know what this means I may be wrong. > >>> > >>> Can anybody tell me what this message means? For example, is it an > >>> indication of incoming I/O on the signaling socket that would account > for an > >>> excessive number of background wakes??? > >>> > >>> > >> > >> > >> First of all please see http://trac.pjsip.org/repos/ticket/1482 for > more > >> info about the problem. The solution mentioned there are part of 1.14 > and > >> 2.0 release, so please upgrade if you're using older version. > >> > >> When app is woken up, UDP sockets are reset by iOS and it needs to be > >> recreated to make it work again. So if anything, the message is just an > >> indication that your app has just been woken up. > >> > >> Cheers > >> 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 > >> > > > > > > > > -- > > Thomas Merriewether > > Star2Star Communications > > > > > > > > _______________________________________________ > > 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 > -- Thomas Merriewether Star2Star Communications -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120628/59853dd1/attachment.html>
