30 Jun
2017
30 Jun
'17
2:07 p.m.
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
30 Jun
30 Jun
2:24 p.m.
Hi.
The TSILO module in kamailio is impelemented for push notifications for
ISO and Android.
Please read its documentations in kamailio website.
With Regards
Mojtaba Esfandiari.S
On 30 Jun 2017 16:37, "Kjeld Flarup" <kfc(a)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(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
2:31 p.m.
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(a)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(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
3:56 p.m.
it is greate share.
Thanks.
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/IOS-10-and-SIP-tp159890p159902.html
Sent from the Users mailing list archive at Nabble.com.
4:28 p.m.
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
<https://www.youtube.com/watch?v=4XIrR9bwUkM>.
And the slides:
https://www.kamailio.org/events/2015-KamailioWorld/Day2/20-Federico.Cabiddu…
<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(a)viptel.dk
<mailto: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 <tel:%2B45%2046949949>, Telefax: +45
46949950 <tel:%2B45%2046949950>, http://viptel.dk
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
5:05 p.m.
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
Le 2017-06-30 à 10:28, Kjeld Flarup a écrit :
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
<https://www.youtube.com/watch?v=4XIrR9bwUkM>.
And the slides:
https://www.kamailio.org/events/2015-KamailioWorld/Day2/20-Federico.Cabiddu…
<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(a)viptel.dk
<mailto: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 <tel:%2B45%2046949949>, Telefax: +45
46949950 <tel:%2B45%2046949950>, http://viptel.dk
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
1 Jul
1 Jul
9:32 a.m.
Hi,
this really depend on your specific scenarios and how you manage users.
For example if your users can have a plain sip phone and one or more
mobiles, you could store the APN or GCM tokens in usr_preferences table.
When an INVITE comes in for a user you first lookup for the registered
contacts and send the INVITE to them, then you send the push request to
your push service for the mobile devices and, if any new contact appears,
you add new branches with tsilo functions.
Or you could choose to always send a push to be sure that the mobile
devices info are "fresh". Personally I prefer in my deployments this
approach and not to store the users' details for the push in Kamailio but
rather delegate an external service for this. But this is my personal
preference, any other approach is valid.
Cheers,
Federico
On Fri, Jun 30, 2017 at 4:28 PM, Kjeld Flarup <kfc(a)viptel.dk> wrote:
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 <+45%2046%2094%2099%2049>, Telefax: +45 46949950
<+45%2046%2094%2099%2050>, 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/D
ay2/20-Federico.Cabiddu-Kamailio-In-A-Mobile-World.pdf.
Cheers,
Federico
On Fri, Jun 30, 2017 at 2:07 PM, Kjeld Flarup <kfc(a)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(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
Kamailio (SER) - Users Mailing
Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
30 Jun
30 Jun
5:35 p.m.
Hi Federico.
I saw your speech at Kamailio world conferance. That's greats. :))
With Regards.
Mojtaba Esfandiari.S
On 30 Jun 2017 17:02, "Federico Cabiddu" <federico.cabiddu(a)gmail.com>
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/D
ay2/20-Federico.Cabiddu-Kamailio-In-A-Mobile-World.pdf.
Cheers,
Federico
On Fri, Jun 30, 2017 at 2:07 PM, Kjeld Flarup <kfc(a)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(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
2492
days inactive
2493
days old
7 comments
5 participants
participants (5)
-
Emmanuel BUU -
Federico Cabiddu -
Kjeld Flarup -
Mojtaba -
ycaner