the PJSIP open source SIP stack ()

Tom Merriewether | 28 Jun 2012 16:04

What does it mean: ioq_select Attempting to replace UDP socket NN

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???

--
Thomas Merriewether

Star2Star Communications

<div>
<p>I am running PJSIP over a TCP proxy on the iPhone.</p>
<div>My app is getting killed with SBUnsuspendLimit exceeded 15 wakes in 300 seconds. &nbsp;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). &nbsp;The application most recently crashed in the background after a flurry of these PJSIP messages:</div>
<div><br></div>
<div>
<div>PLOG --&gt; 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.872 &nbsp; &nbsp; ioq_select &nbsp;UDP has been replaced successfully!</div>
<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.872 &nbsp; &nbsp; ioq_select &nbsp;Attempting to replace UDP socket 45</div>
<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.872 &nbsp; &nbsp; ioq_select &nbsp;UDP has been replaced successfully!</div>
<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.873 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.873 &nbsp; &nbsp; ioq_select &nbsp;Attempting to replace UDP socket 46</div>
<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.873 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.873 &nbsp; &nbsp; ioq_select &nbsp;UDP has been replaced successfully!</div>
<div><br></div>
<div>I'm not reading this as a flurry of incoming packets on the SIP signaling socket, &nbsp;but since I don't know what this means I may be wrong.&nbsp;</div>
<div><br></div>
<div>Can anybody tell me what this message means? &nbsp;For example, &nbsp;is it an indication of incoming I/O on the signaling socket that would account for an excessive number of background wakes???</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>-- <br>Thomas Merriewether<div>Star2Star Communications</div>
<div><br></div>
<br>
</div>
</div>

headers

Benny Prijono | 29 Jun 2012 01:03

Re: What does it mean: ioq_select Attempting to replace UDP socket NN

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

<div>
<p>On Thu, Jun 28, 2012 at 9:04 PM, Tom Merriewether <span dir="ltr">&lt;<a href="mailto:tmerriewether <at> star2star.com" target="_blank">tmerriewether <at> star2star.com</a>&gt;</span> wrote:<br></p>
<div class="gmail_quote">
<blockquote class="gmail_quote">
I am running PJSIP over a TCP proxy on the iPhone.<div>My app is getting killed with SBUnsuspendLimit exceeded 15 wakes in 300 seconds. &nbsp;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). &nbsp;The application most recently crashed in the background after a flurry of these PJSIP messages:</div>

<div><br></div>
<div>
<div>PLOG --&gt; 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.872 &nbsp; &nbsp; ioq_select &nbsp;UDP has been replaced successfully!</div>
<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.872 &nbsp; &nbsp; ioq_select &nbsp;Attempting to replace UDP socket 45</div>

<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.872 &nbsp; &nbsp; ioq_select &nbsp;UDP has been replaced successfully!</div>
<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.873 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.873 &nbsp; &nbsp; ioq_select &nbsp;Attempting to replace UDP socket 46</div>

<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.873 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.873 &nbsp; &nbsp; ioq_select &nbsp;UDP has been replaced successfully!</div>
<div><br></div>
<div>I'm not reading this as a flurry of incoming packets on the SIP signaling socket, &nbsp;but since I don't know what this means I may be wrong.&nbsp;</div>

<div><br></div>
<div>Can anybody tell me what this message means? &nbsp;For example, &nbsp;is it an indication of incoming I/O on the signaling socket that would account for an excessive number of background wakes???</div>
<span class="HOEnZb"><div>
<br>
</div>
<div><br></div></span>
</div>
</blockquote>
<div>
<br><br>
</div>
</div>First of all please see <a href="http://trac.pjsip.org/repos/ticket/1482">http://trac.pjsip.org/repos/ticket/1482</a> 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.<br><br>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.<br><br>Cheers<br>&nbsp;Benny<br><br>
</div>

headers

Tom Merriewether | 29 Jun 2012 04:57

Re: What does it mean: ioq_select Attempting to replace UDP socket NN

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

Attachment (monitoredCrash.log.zip): application/zip, 35 KiB

<div>
<p>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. &nbsp;I'll attach a text log of what is going on. &nbsp;This seems to happen spontaneously. &nbsp;The log is long but if you scroll down to the end you can see what I am saying. &nbsp;It appears to work some of the time but then gets lost in the weeds later.</p>
<div>
<br>
</div>
<div>I inherited version 1.10 and have been hesitant to move to 2.0. &nbsp;I tried a simpleminded approach. &nbsp;I built the libraries for 2.0 and just swapped the new libs for the old. &nbsp;Crashed on startup. &nbsp;So if I move to 2.0 &nbsp;is there some sort of a guide for changed API 1.X --&gt; 2.0? &nbsp;I am a PJSIP newcomer and just plowing into this is a bit intimidating, &nbsp;but I see your point.</div>
<div><br></div>
<div>
<br><br><div class="gmail_quote">On Thu, Jun 28, 2012 at 7:03 PM, Benny Prijono <span dir="ltr">&lt;<a href="mailto:bennylp <at> teluu.com" target="_blank">bennylp <at> teluu.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div class="HOEnZb"><div class="h5">On Thu, Jun 28, 2012 at 9:04 PM, Tom Merriewether <span dir="ltr">&lt;<a href="mailto:tmerriewether <at> star2star.com" target="_blank">tmerriewether <at> star2star.com</a>&gt;</span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote">
I am running PJSIP over a TCP proxy on the iPhone.<div>My app is getting killed with SBUnsuspendLimit exceeded 15 wakes in 300 seconds. &nbsp;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). &nbsp;The application most recently crashed in the background after a flurry of these PJSIP messages:</div>

<div><br></div>
<div>
<div>PLOG --&gt; 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.872 &nbsp; &nbsp; ioq_select &nbsp;UDP has been replaced successfully!</div>
<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.872 &nbsp; &nbsp; ioq_select &nbsp;Attempting to replace UDP socket 45</div>

<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.872 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.872 &nbsp; &nbsp; ioq_select &nbsp;UDP has been replaced successfully!</div>
<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.873 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.873 &nbsp; &nbsp; ioq_select &nbsp;Attempting to replace UDP socket 46</div>

<div><br></div>
<div>PLOG --&gt; 2012-06-27 18:38:51.873 Star2Star[158:7303] SIP PJSIP message: &nbsp;18:38:51.873 &nbsp; &nbsp; ioq_select &nbsp;UDP has been replaced successfully!</div>
<div><br></div>
<div>I'm not reading this as a flurry of incoming packets on the SIP signaling socket, &nbsp;but since I don't know what this means I may be wrong.&nbsp;</div>

<div><br></div>
<div>Can anybody tell me what this message means? &nbsp;For example, &nbsp;is it an indication of incoming I/O on the signaling socket that would account for an excessive number of background wakes???</div>
<span><div>

<br>
</div>
<div><br></div></span>
</div>
</blockquote>
<div>
<br><br>
</div>
</div>
</div></div>First of all please see <a href="http://trac.pjsip.org/repos/ticket/1482" target="_blank">http://trac.pjsip.org/repos/ticket/1482</a> 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.<br><br>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.<br><br>Cheers<span class="HOEnZb"><br>
&nbsp;Benny<br><br></span><br>_______________________________________________<br>
Visit our blog: <a href="http://blog.pjsip.org" target="_blank">http://blog.pjsip.org</a><br><br>
pjsip mailing list<br><a href="mailto:pjsip <at> lists.pjsip.org">pjsip <at> lists.pjsip.org</a><br><a href="http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org" target="_blank">http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org</a><br><br>
</blockquote>
</div>
<br><br clear="all"><div><br></div>-- <br>Thomas Merriewether<div>Star2Star Communications</div>
<div><br></div>
<br>
</div>
</div>

headers

Ming | 29 Jun 2012 05:02

Re: What does it mean: ioq_select Attempting to replace UDP socket NN

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
>

headers

Tom Merriewether | 29 Jun 2012 05:11

Re: What does it mean: ioq_select Attempting to replace UDP socket NN

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

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