After sending the initial push notification, don’t send additional push notifications to cancel the call or communicate new details to your app. Instead, communicate with the app directly over the network connection you established between it and your server.

Hello, On Cancel we are sending just another Push Notification that indicates the call is cancelled, and the calling screen dissapear. Regards, On Wed 10 Mar 2021 at 12:28, Igor Olhovskiy &lt;igorolhovskiy(a)gmail.com <mailto:igorolhovskiy@gmail.com>> wrote: Hello! Is there any way to "store" already finished transactions in tsilo? Idea is to deliver, for example, canceled calls to the phone, when call already was answered on other device, but push notification arrive later? Major problem here, that there how it's working on iOS. On iOS phone first show you calling screen, than - app is waking and after app will register and receive invite with tsilo, it updates calling screen with CallerID and other info. But if call was canceled before, calling screen is shown, but app not receiving INVITE, so, call screen is just there for some timeout (for Linphone, for ex, it's 20 sec). Right now I've manage to do it via external SIPP call, that emulates "fake missed call", but maybe there is other way to "store" already dead transactions for some time? PS: Unfortunately, can't solve this on mobile app level. -- Regards, Igor _______________________________________________ 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 <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>