[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] iOS5 background - waking 15 times in 300 secon

From: Ramu
Subject: Re: [Linphone-developers] iOS5 background - waking 15 times in 300 seconds kicking the app
Date: Tue, 22 Nov 2011 15:50:10 +0530


I tested the Linphone app on iOS5 and did ethereal on server.  Server is not sending keep alive messages.

The reason is :
1) when we enter into background, we are not invalidating timer thread i.e mIterateTimer
2) this timer invoking iterate method for every 0.1 sec i.e 100 ms.

I think to fix this issue we need to do following things
1) Invalidate the timer when we are entering into background
2) And register our VOIP socket with CFReadStreamSetProperty

We are using TCP protocol in Linphone with OpenSIPs Server.

On Fri, Nov 18, 2011 at 10:31 PM, Jehan Monnier <address@hidden> wrote:
Again, this is probably because the sip server is sending keep alive.
Double check with ethereal.


Le 18 nov. 2011 à 17:57, Ramu a écrit :

Hi Users/Developers,

It is such critical item and no one is talking about to this issue.

Jehan can you please shed some light here?

---------- Forwarded message ----------
From: Ramu <address@hidden>
Date: Fri, Nov 18, 2011 at 12:13 AM
Subject: iOS5 background - waking 15 times in 300 seconds kicking the app
To: linphone-developers <address@hidden>, linphone-users <address@hidden>

Recently with iOS5 we’ve noticed we’re having these issues

Application Specific Information:
SBUnsuspendLimit O2 Connect[293] exceeded 15 wakes in 300 sec

The application is being kicked out by the OS.

We are using an OpenSIPS server, registration set to 10 minutes (so we can use the iphone wakeup and re-reg background timed event).

The problem is that this happens intermittantly.. ie: something is really coming up and triggering excessive socket/background wakeups.

Just wondering if anyone else is experiencing this and if they’ve be able to tune the app behaviour or else the server behaviour..



reply via email to

[Prev in Thread] Current Thread [Next in Thread]