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@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-… Regards, Federico On Fri, Jun 10, 2016 at 10:41 AM, gmele <giovanni.mele@nagra.com<mailto:giovanni.mele@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-tp1493… Sent from the Users mailing list archive at Nabble.com. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hi Federico, Correct me if I’m wrong, but the INVITE will be sent to all user entries registered in the location table, right? If both the desktop client and the mobile phone are registered in this table, but the mobile contact info incorrect (wrong ip/port), how Kamailio will handle the tcp_connect error (we are using TLS btw)? Supposing Kamailio handle the connection failure to the mobile phone, in our config, after having sent the INVITE, we do the push notifs and when the REGISTER are coming back from the phone, we append the new branch for it, but how will the INVITE be sent to the phone? Of course, then we have also the case where the location table contains correct contact info, for both mobile and desktop VoIP apps. In this case, the INVITE will be sent correctly to both clients, but we will also do a push notif to the phone… how handle this? Lots of questions, but it is not easy to handle phones and desktop clients…. Regards Giovanni From: Federico Cabiddu-3 [via SIP Router] [mailto:ml-node+s1086192n149395h11@n5.nabble.com] Sent: vendredi 10 juin 2016 11:15 To: Mele Giovanni Subject: Re: TM Module t_suspend question 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 <[hidden email]</user/SendEmail.jtp?type=node&node=149395&i=0>> 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:[hidden email]</user/SendEmail.jtp?type=node&node=149395&i=1>] 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-… Regards, Federico On Fri, Jun 10, 2016 at 10:41 AM, gmele <[hidden email]</user/SendEmail.jtp?type=node&node=149395&i=2>> 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-tp1493… Sent from the Users mailing list archive at Nabble.com. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list [hidden email]</user/SendEmail.jtp?type=node&node=149395&i=3> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list [hidden email]</user/SendEmail.jtp?type=node&node=149395&i=4> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list [hidden email]</user/SendEmail.jtp?type=node&node=149395&i=5> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ________________________________ If you reply to this email, your message will be added to the discussion below: http://sip-router.1086192.n5.nabble.com/TM-Module-t-suspend-question-tp1493… To unsubscribe from TM Module t_suspend question, click here<http://sip-router.1086192.n5.nabble.com/template/NamlServlet.jtp?ma…U2MDgyNTA0>. NAML<http://sip-router.1086192.n5.nabble.com/template/NamlServlet.jtp?ma… -- View this message in context: http://sip-router.1086192.n5.nabble.com/TM-Module-t-suspend-question-tp1493… Sent from the Users mailing list archive at Nabble.com.

Hi Federico, Thx for your great help. We will update our config and see how it works. Ciao Giovanni Mele Le 10 juin 2016 à 11:56, "Federico Cabiddu-3 [via SIP Router]" <ml-node+s1086192n149400h66@n5.nabble.com<mailto:ml-node+s1086192n149400h66@n5.nabble.com>> a écrit : Hi Giovanni, see my answers inline On Fri, Jun 10, 2016 at 11:29 AM, gmele <[hidden email]</user/SendEmail.jtp?type=node&node=149400&i=0>> wrote: Hi Federico, Correct me if I’m wrong, but the INVITE will be sent to all user entries registered in the location table, right? If both the desktop client and the mobile phone are registered in this table, but the mobile contact info incorrect (wrong ip/port), how Kamailio will handle the tcp_connect error (we are using TLS btw)? with the tcpops module you can enable the event route for the socket closure: http://www.kamailio.org/docs/modules/devel/modules/tcpops.html#tcpops.f.tcp… In the event route you can then implement the logic to send again a push to trigger a new registration. Supposing Kamailio handle the connection failure to the mobile phone, in our config, after having sent the INVITE, we do the push notifs and when the REGISTER are coming back from the phone, we append the new branch for it, but how will the INVITE be sent to the phone? ts_append() will append the new branch(es) and send them. No need to explicitly send the INVITE to the new branches. Of course, then we have also the case where the location table contains correct contact info, for both mobile and desktop VoIP apps. In this case, the INVITE will be sent correctly to both clients, but we will also do a push notif to the phone… how handle this? If the client registers again while there is already an ongoing branch for the same contact, tsilo won't append a new branch for it, so it is safe to register while there is a stored transaction. Lots of questions, but it is not easy to handle phones and desktop clients…. Regards Giovanni Regards, Federico From: Federico Cabiddu-3 [via SIP Router] [mailto:[hidden email]</user/SendEmail.jtp?type=node&node=149400&i=1>[hidden email]<http:///user/SendEmail.jtp?type=node&node=149397&i=0>] Sent: vendredi 10 juin 2016 11:15 To: Mele Giovanni Subject: Re: TM Module t_suspend question 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 <[hidden email]<http:///user/SendEmail.jtp?type=node&node=149395&i=0>> 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:[hidden email]<http:///user/SendEmail.jtp?type=node&node=149395&i=1>] 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-… Regards, Federico On Fri, Jun 10, 2016 at 10:41 AM, gmele <[hidden email]<http:///user/SendEmail.jtp?type=node&node=149395&i=2>> 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-tp1493… Sent from the Users mailing list archive at Nabble.com<http://Nabble.com>. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list [hidden email]<http:///user/SendEmail.jtp?type=node&node=149395&i=3> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list [hidden email]<http:///user/SendEmail.jtp?type=node&node=149395&i=4> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list [hidden email]<http:///user/SendEmail.jtp?type=node&node=149395&i=5> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ________________________________ If you reply to this email, your message will be added to the discussion below: http://sip-router.1086192.n5.nabble.com/TM-Module-t-suspend-question-tp1493… To unsubscribe from TM Module t_suspend question, click here. NAML<http://sip-router.1086192.n5.nabble.com/template/NamlServlet.jtp?ma… ________________________________ View this message in context: RE: TM Module t_suspend question<http://sip-router.1086192.n5.nabble.com/TM-Module-t-suspend-que… Sent from the Users mailing list archive<http://sip-router.1086192.n5.nabble.com/Users-f3.html> at Nabble.com<http://Nabble.com>. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list [hidden email]</user/SendEmail.jtp?type=node&node=149400&i=2> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list [hidden email]</user/SendEmail.jtp?type=node&node=149400&i=3> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ________________________________ If you reply to this email, your message will be added to the discussion below: http://sip-router.1086192.n5.nabble.com/TM-Module-t-suspend-question-tp1493… To unsubscribe from TM Module t_suspend question, click here<http://sip-router.1086192.n5.nabble.com/template/NamlServlet.jtp?ma…U2MDgyNTA0>. NAML<http://sip-router.1086192.n5.nabble.com/template/NamlServlet.jtp?ma… -- View this message in context: http://sip-router.1086192.n5.nabble.com/TM-Module-t-suspend-question-tp1493… Sent from the Users mailing list archive at Nabble.com.