Thanks so much for thes information.

I understand that Apple is looking to optimize the battery lifetime but this basically forces all softphone developpers for iOS to build a dependency to Apple infrastructure.

If I understand the implication correctly, this means that the softphone vendor will need to provide an infrastructure JUST for waking up the app.

Sorry for the rant but this is stupid ! They should have enable a couple of signalling protocols such as SIP to register a way to wake up a background app ...

But I guess this is the new "open" world dominated by a couple of giant companies that we live in. We have no choice. So much for open and standard protocols.

/Manu

Thanks Frederico

Thanks for that. The Tsilo module simplifies this a lot.

One thing I still see as a challenge is in the multi client scenario, where we may have a plain SIP phone, an IOS and an Android. How to manage which push to enable, or do we always try to push.

Med venlig hilsen / Best regards
Kjeld Flarup (Christensen) M.Sc E.E, Teknisk chef 
Viptel ApS, Hammershusvej 16C, DK-7400 Herning
Telefon: +45 46949949, Telefax: +45 46949950, http://viptel.dk

On 2017-06-30 14:31, Federico Cabiddu wrote:

Hi,

good news: you can easily handle this scenario with Kamailio!

If you want to have an overall view of VoIP&Push&Kamailio you can have a look at this speech I gave at Kamailio World 2015: https://www.youtube.com/watch?v=4XIrR9bwUkM.

And the slides: https://www.kamailio.org/events/2015-KamailioWorld/Day2/20-Federico.Cabiddu-Kamailio-In-A-Mobile-World.pdf.

Cheers,

Federico

On Fri, Jun 30, 2017 at 2:07 PM, Kjeld Flarup <kfc@viptel.dk> wrote:

Rumours is that Apple no longer accepts apps which can do persistent connections in the background.

To my best knowledge that means that IOS no longer supports SIP incoming calls.
The app should now use Push Notifications, but SIP does not support this.

Anybody faced this problem?

Is the solution to call an external program when processing an Invite? This leaves some issues.

1. Should we wait some seconds before proceeding or wait until the Push notification has been processed, to give the app time to register.
We cannot start to send invites, before we have a correct registration. An old registration may change ports when the app wakes up and makes a new register via NAT.

2. How do we know, if a given user should have a push notification?

3. Which information do we need to be able to send the push notification?

4. Does this give a penalty to Android users, because we have to wait for IOS?



--
Med venlig hilsen / Best regards
Kjeld Flarup (Christensen) M.Sc E.E, Teknisk chef
Viptel ApS, Hammershusvej 16C, DK-7400 Herning
Telefon: +45 46949949, Telefax: +45 46949950, http://viptel.dk


_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users