[SR-Users] Dealing with mobile client state while using Push Notification and TSILO

Hubert Odziemczyk hubert.odziemczyk at cern.ch
Thu Apr 16 14:38:27 CEST 2020


Hello!

We are trying to setup a call-flow with TSILO and Push Notifications for solution with a mobile SIP client (Linphone), based on presentation by Federico Cabiddu (http://www.kamailio.org/events/2015-KamailioWorld/Day2/20-Federico.Cabiddu-Kamailio-In-A-Mobile-World.pdf).

We have an issue with "managing" state of the client (active or not) when there is a call coming. To be more specific, lookup in location table doesn't always give a proper answer, as contact expiration is different from actual lifetime of the app (which also differs between iOS and Android).
One of proposed solutions is setting Expires=1 for REGISTER and then always rely on Push Notifications, but this scenario seems to be unreliable with some clients that are in foreground, as Push Notification doesn't trigger REGISTER again.

Question is: did you perceive similar problems? What are your solutions to deal with them?

Thank you in advance!

Best regards,
Hubert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20200416/2104a587/attachment.html>


More information about the sr-users mailing list