[Top][All Lists]

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

Re: [Linphone-developers] latest linphone on iOS 8 closes background con

From: Peter Villeneuve
Subject: Re: [Linphone-developers] latest linphone on iOS 8 closes background connections
Date: Wed, 11 Feb 2015 17:32:47 +0000

Hi guys,

Thanks for helping out guys.
I'm using the latest linphone from itunes so it should be ok with iOS 8.

I have checked the app permissions in iOS settings and everything's OK.
The app doesn't lose connection right away and the server (kamailio proxy in my case) reports the correct IP and calls work normally.
In my latest test, the app stayed registered on the server for 30 something minutes (user was on wifi) and then it went offline when he went to lunch.

Not sure what's causing this. Could it be that when the user moves from wifi to 3G the app starts to think it has no connection to the internet and won't attempt to reconnect to the SIP proxy until the user manually opens it?
I figured if that were the case the app would attempt to reconnect to the server periodically, which doesn't happen. The only way to get the user back online is for him to open linphone again (although linphone is stull there in the mutlitasking list when the user double presses the home button). This "reawakening" of linphone also works when he's on 3G, so that tends to rule out Vodafone blocking SIP. Besides I have been able to call him when he's on 3G.

Not really sure why this happens to some iPhones and not others (that are always registered on the server like their android brothers).

If anyone has any more thoughts on what's happening or other tests I could run please feel free to share.


On Wed, Feb 11, 2015 at 12:55 PM, Ákos Szente <address@hidden> wrote:
Apple has made some changes to the local notification API in iOS8. These changes have already been implemented in Linphone months ago. 

Are you using the latest Linphone or did you fork an older version? If you're using an older version, see this question on StackOverflow: 

Check your device logs because iOS should dispatch a warning about the deprecated API through ASL. 

registerForRemoteNotificationTypes: is not supported in iOS 8.0 and later.
If you're using the latest version then I don't really have any idea. Works fine for us. 


On 11 February 2015 at 05:03, Henrik Husted <address@hidden> wrote:
Hi Peter 

We're having a similar setup and don't see any problems. Right now I'm on iOS 8 connected to a Freeswitch server on a TLS connection. 
Your issue could be a number of things. 

Have you checked that your app permissions are okay? There should be an entry in iOS settings for your app with the permissions to run in the background are enabled. 

Does the app lose connection straight after entering background mode? Or does it take a few minutes? 
Does the SIP server say that the user is still online and with the correct IP? I guess all this should be fine since it works on iOS 7. 

My best guess is that background permissions are not properly set. 


On 10/02/2015, at 21.34, Peter Villeneuve <address@hidden> wrote:

Anyone else using linphone on iOS?

Can you please confirm this behaviour?



On Mon, Feb 9, 2015 at 3:35 PM, Peter Villeneuve <address@hidden> wrote:

Has anyone else noticed that iPhones that have iOS 8 seem to lose their registrations on the SIP servers?

I have my own SIP (kamailio) proxy setup with TLS (yes I know that iOS closes UDP sockets after some minutes), and it seems that iPhones that are still on iOS 7 stay registered in the background as they should, while iPhones with the newer IOS 8 seem to go offline and stay offline until the app is opened.

I have the exact same settings setup for both iPhones (with iOS 7 and iOS8), so that shouldn't be the problem:
TLS transport, Proxy set, Outbound Proxy checked, Edge Optimization checked.

Has something relevant changed with iOS 8? Has anyone managed to keep linphone registered in the background with iOS 8?



Linphone-developers mailing list

Linphone-developers mailing list

Linphone-developers mailing list

reply via email to

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