7 Dec
2016
7 Dec
'16
2:32 a.m.
Hello, my goal is to address iOS 10's removal of periodic TCP connections
in iOS apps with their replacement PushKit, a push-based alternative all
VoIP apps should implement.
In order to have iOS apps receive SIP calls in the background, I believe I
need to use tsilo to suspend the INVITE transaction send a push
notification to the device. I have been following the presentation here (
http://www.kamailio.org/events/2015-KamailioWorld/Day2/20-Federico.Cabiddu-…)
however I am not sure how to integrate it with Asterisk (
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
).
My questions can be summarized below:
(1) What changes need to be made from Federico's presentation to use with
the Kamailio/Asterisk integration?
(2) How can I modify the config to send push notifications for EVERY
invite? This is to address the scenario where a device goes offline before
the SIP registration expires and a call is received within that window. iOS
is very aggressive about killing background applications so it's likely as
soon as user leaves the VoIP app, the device will become unreachable.
Thanks for any help.
Benjamin Fitzgerald
LETS Corporation
(925) 235-1154
ben(a)letscorp.us
11 Dec
11 Dec
5:46 p.m.
Hi Benjamin,
if you don't plan to support multiple devices per account just the
t_suspend/t_continue pair should be enough to support push notification.
This being said you can easily integrate the example in my presentation in
the Kamailio's configuration given in the Asterisk/Kamailio integration
page.
For the INVITE you have to modify the route[LOCATION] and, instead of
performing the lookup, suspend the transaction and send the push. In this
way you'll also send the push for every INVITE, regardless of the
registration state. You have then to modify the REGISTRAR route after
calling save() to resume the transaction or to append new branches (if you
use tsilo). I think that the snippets from my example should be enough.
Hope this helps.
Regards,
Federico
On Wed, Dec 7, 2016 at 2:32 AM, Benjamin Fitzgerald <ben(a)letscorp.us> wrote:
Hello, my goal is to address iOS 10's removal of
periodic TCP connections
in iOS apps with their replacement PushKit, a push-based alternative all
VoIP apps should implement.
In order to have iOS apps receive SIP calls in the background, I believe I
need to use tsilo to suspend the INVITE transaction send a push
notification to the device. I have been following the presentation here (
http://www.kamailio.org/events/2015-KamailioWorld/
Day2/20-Federico.Cabiddu-Kamailio-In-A-Mobile-World.pdf) however I am not
sure how to integrate it with Asterisk (http://kb.asipto.com/
asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb).
My questions can be summarized below:
(1) What changes need to be made from Federico's presentation to use with
the Kamailio/Asterisk integration?
(2) How can I modify the config to send push notifications for EVERY
invite? This is to address the scenario where a device goes offline before
the SIP registration expires and a call is received within that window. iOS
is very aggressive about killing background applications so it's likely as
soon as user leaves the VoIP app, the device will become unreachable.
Thanks for any help.
Benjamin Fitzgerald
LETS Corporation
(925) 235-1154
ben(a)letscorp.us
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
12 Dec
12 Dec
7:41 a.m.
Hi,
I didn't mention in my reply, and it wasn't probably clear, that Kamailio
won't send the actual push to Apple or Google (for GCM).
This needs to be implemented separately, either with a self written service
or using a web service like the Amazon's one.
In the example from my presentation the call to
lua_runstring("do_push([[$hdr(X-VxTo)]], [[$tU]], [[$hdr(XVxFrom)]],
[[$fU]], [[$ci]])")<0)
is actually just an example of where, in the Kamailio script, the logic for
sending the push should be placed.
Regards,
Federico
On Sun, Dec 11, 2016 at 5:46 PM, Federico Cabiddu <
federico.cabiddu(a)gmail.com> wrote:
Hi Benjamin,
if you don't plan to support multiple devices per account just the
t_suspend/t_continue pair should be enough to support push notification.
This being said you can easily integrate the example in my presentation in
the Kamailio's configuration given in the Asterisk/Kamailio integration
page.
For the INVITE you have to modify the route[LOCATION] and, instead of
performing the lookup, suspend the transaction and send the push. In this
way you'll also send the push for every INVITE, regardless of the
registration state. You have then to modify the REGISTRAR route after
calling save() to resume the transaction or to append new branches (if you
use tsilo). I think that the snippets from my example should be enough.
Hope this helps.
Regards,
Federico
On Wed, Dec 7, 2016 at 2:32 AM, Benjamin Fitzgerald <ben(a)letscorp.us>
wrote:
Hello, my goal is to address iOS 10's removal
of periodic TCP connections
in iOS apps with their replacement PushKit, a push-based alternative all
VoIP apps should implement.
In order to have iOS apps receive SIP calls in the background, I believe
I need to use tsilo to suspend the INVITE transaction send a push
notification to the device. I have been following the presentation here (
http://www.kamailio.org/events/2015-KamailioWorld/Day2/20-
Federico.Cabiddu-Kamailio-In-A-Mobile-World.pdf) however I am not sure
how to integrate it with Asterisk (http://kb.asipto.com/asterisk
:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb).
My questions can be summarized below:
(1) What changes need to be made from Federico's presentation to use with
the Kamailio/Asterisk integration?
(2) How can I modify the config to send push notifications for EVERY
invite? This is to address the scenario where a device goes offline before
the SIP registration expires and a call is received within that window. iOS
is very aggressive about killing background applications so it's likely as
soon as user leaves the VoIP app, the device will become unreachable.
Thanks for any help.
Benjamin Fitzgerald
LETS Corporation
(925) 235-1154
ben(a)letscorp.us
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
10:10 p.m.
Thanks Federico,
That's very clear. I will try your suggestions to see if I can get it
working. I am using AWS SNS for notifications, so I have the script to do
the actual push working on it's own already.
Benjamin Fitzgerald
LETS Corporation
(925) 235-1154
ben(a)letscorp.us
*******Confidential Notice:
This message is intended only for the use of the individual or entity to
which it is addressed and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this message in error, please
delete this message from all computers and contact Orion Systems/LETS Corp
immediately by return e-mail and/or telephone at (925) 566-5600
On Sun, Dec 11, 2016 at 10:41 PM, Federico Cabiddu <
federico.cabiddu(a)gmail.com> wrote:
Hi,
I didn't mention in my reply, and it wasn't probably clear, that Kamailio
won't send the actual push to Apple or Google (for GCM).
This needs to be implemented separately, either with a self written
service or using a web service like the Amazon's one.
In the example from my presentation the call to
lua_runstring("do_push([[$hdr(X-VxTo)]], [[$tU]], [[$hdr(XVxFrom)]],
[[$fU]], [[$ci]])")<0)
is actually just an example of where, in the Kamailio script, the logic
for sending the push should be placed.
Regards,
Federico
On Sun, Dec 11, 2016 at 5:46 PM, Federico Cabiddu <
federico.cabiddu(a)gmail.com> wrote:
Hi Benjamin,
if you don't plan to support multiple devices per account just the
t_suspend/t_continue pair should be enough to support push notification.
This being said you can easily integrate the example in my presentation
in the Kamailio's configuration given in the Asterisk/Kamailio integration
page.
For the INVITE you have to modify the route[LOCATION] and, instead of
performing the lookup, suspend the transaction and send the push. In this
way you'll also send the push for every INVITE, regardless of the
registration state. You have then to modify the REGISTRAR route after
calling save() to resume the transaction or to append new branches (if you
use tsilo). I think that the snippets from my example should be enough.
Hope this helps.
Regards,
Federico
On Wed, Dec 7, 2016 at 2:32 AM, Benjamin Fitzgerald <ben(a)letscorp.us>
wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello, my goal is to address iOS 10's removal
of periodic TCP
connections in iOS apps with their replacement PushKit, a push-based
alternative all VoIP apps should implement.
In order to have iOS apps receive SIP calls in the background, I believe
I need to use tsilo to suspend the INVITE transaction send a push
notification to the device. I have been following the presentation here (
http://www.kamailio.org/events/2015-KamailioWorld/Day2/20-F
ederico.Cabiddu-Kamailio-In-A-Mobile-World.pdf) however I am not sure
how to integrate it with Asterisk (http://kb.asipto.com/asterisk
:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb).
My questions can be summarized below:
(1) What changes need to be made from Federico's presentation to use
with the Kamailio/Asterisk integration?
(2) How can I modify the config to send push notifications for EVERY
invite? This is to address the scenario where a device goes offline before
the SIP registration expires and a call is received within that window. iOS
is very aggressive about killing background applications so it's likely as
soon as user leaves the VoIP app, the device will become unreachable.
Thanks for any help.
Benjamin Fitzgerald
LETS Corporation
(925) 235-1154
ben(a)letscorp.us
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
2714
days inactive
2719
days old
3 comments
2 participants
participants (2)
-
Benjamin Fitzgerald -
Federico Cabiddu