[SR-Users] TM Module t_suspend question

[Federico Cabiddu]

Hi Giovanni,
in this case, supposing that the desktop client is registered, you send the
INVITE to it, you store the transaction and you send the push WITHOUT
suspending the transaction. Then you append to the transaction additional
branch(es) as soon as the mobile client register.
I hope I understood your scenario.
Regards,

Federico

On Fri, Jun 10, 2016 at 11:09 AM, Mele Giovanni <giovanni.mele at nagra.com>
wrote:

> Hello Federico,
>
>
>
> Thx for you input. We are effectively using TS_SILO module to store the
> transactions. The link to your presentation is very interesting! Grazie!
>
>
>
> In your presentation, the multi-device scenario assumes all devices are
> able to receive push notifs, but what happens if you have one device that
> doesn’t support it, like a Windows based desktop VoIP client?
>
>
>
>
>
> Regards
>
>
>
>
>
> Giovanni
>
>
>
>
>
> *From:* sr-users [mailto:sr-users-bounces at lists.sip-router.org] *On
> Behalf Of *Federico Cabiddu
> *Sent:* vendredi 10 juin 2016 10:48
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] TM Module t_suspend question
>
>
>
> Hi,
>
> for this kind of scenarios I'd suggest to use the TSILO module which have
> been thought for mobile multidevice scenarios:
>
> http://www.kamailio.org/docs/modules/devel/modules/tsilo.html.
>
>
>
> Basically what you can do is: send the INVITE to the desktop phone, store
> the transaction, send the push to wake up the mobile app, append a branch
> to the stored transaction as soon as the mobile app registers.
>
>
>
> In my last year's presentation at Kamailio World I give an example of
> TSILO usage:
>
>
>
>
> http://www.kamailio.org/events/2015-KamailioWorld/Day2/20-Federico.Cabiddu-Kamailio-In-A-Mobile-World.pdf
>
>
>
> Regards,
>
>
>
> Federico
>
>
>
> On Fri, Jun 10, 2016 at 10:41 AM, gmele <giovanni.mele at nagra.com> wrote:
>
> Hello,
>
> we are using the TM Module* t_suspend *function in our kamailio to suspend
> transactions (mainly INVITE requests). We do this as we send some push
> notification to the callee that will force it to re-REGISTER. Once we get
> the REGISTER, we resume the transaction with a *t_continue()*.
>
> If the callee never re-REGISTER, the FR Timer will terminate the INVITE
> transaction.
>
> This is working fine for us when the callee has a phone that can receive
> the
> push notification.
>
>
> Now, we want to be able to contact users having multiple devices: phone and
> desktop VoIP clients. The problem with current implementation is that if we
> wait for the re-REGISTER from the mobile phone, we may never send the
> INVITE
> to the desktop VoIP client if the mobile phone is shutdown.
>
> So, I'd like to now if it is possible to set a timer to the t_suspend
> command which will automatically resume the suspended transaction (without
> issuing  an ERROR like the FR timer is doing)? I didn't see such
> possibility
> in the TM module, but is there another way to implement this?
>
> Hope I was clear enough
>
>
> Regards
>
>
> Giovanni
>
>
>
>
> --
> View this message in context:
> http://sip-router.1086192.n5.nabble.com/TM-Module-t-suspend-question-tp149391.html
> Sent from the Users mailing list archive at Nabble.com.
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160610/a71c0ab1/attachment.html>