SIP connection alive in the background or terminated situation

AungKOO commented 1 year ago

For my project, I used Flutter webRTC, sip, flutter incoming call kit, and FCM for incoming calls. But whenever the user exits the app with the back button, the SIP connection is terminated and my backend server can't know it is still alive. Whenever incoming calls are there, Although FCM and Flutter incoming call kit can wake my app and open the app with sip registration at initialization, I cannot know the current SIP state of incoming calls. So, it makes the app open but nothing. Are there any possible ways to keep SIP connection alive in background or terminated situation? I know there may be drawbacks such as devices battery draining or security issues. But it is okay for me if I can keep SIP state connection alive.

pogenz45 commented 1 year ago

I've tried staying connected SIP when the app is terminate in iOS using silent push notification (push notifications/VoIP push), but it doesn't work. Because, when the user terminates the application, iOS will not prioritize your background task. When you use silent notification to run background task, the iOS operating system will depend on the battery, resources, ... to decide which task to prioritize. So silent push notification is not stable (when app in terminate, in first push notification, it not working. I must push 2,3 times to run my background task).

So, here my solution: In the Event.actionCallAccept (note Event.actionCallIncoming not working when app terminate) of the flutter_incoming_callkit library, I will call the registration SIP function when user press button accept (in callkit).

Sound a great solution. Do you try it? Does it work?

pogenz45 commented 1 year ago

but in this situation, when i open app, app does not navigate to callScreen(Screen has 2 button accept and reject call). it mean when click accept from callkit to wake app, app running but not receive event call coming.How can you handle this?

anhquangtech commented 1 year ago

If transaction state is accepted -> navigate to call screen.

pogenz45 commented 1 year ago

but in this situation, when i open app, app does not navigate to callScreen(Screen has 2 button accept and reject call). it mean when click accept from callkit to wake app, app running but not receive event call coming.How can you handle this?

You can check SIP state after re-register success. If transaction state is STREAM, you need accept VoIP call to change transaction state is ACCEPTED. If transaction state is ACCEPTED -> navigate to call screen.

i'll try, thank you very much. Are you vietnamese?

anhquangtech commented 1 year ago

i'll try, thank you very much. Are you vietnamese?

Yes, I am 🤩

pogenz45 commented 1 year ago

but in this situation, when i open app, app does not navigate to callScreen(Screen has 2 button accept and reject call). it mean when click accept from callkit to wake app, app running but not receive event call coming.How can you handle this?

You can check SIP state after re-register success. If transaction state is STREAM, you need accept VoIP call to change transaction state is ACCEPTED. If transaction state is ACCEPTED -> navigate to call screen.

i'll try, thank you very much. Are you vietnamese?

Yes, I am 🤩

Ok anh, em sẽ thử theo cách của anh. Có khó khăn j mong anh giúp đỡ em với nhé.

pogenz45 commented 7 months ago

i'll try, thank you very much. Are you vietnamese?

Yes, I am 🤩

anh ơi cho em hỏi khi có 1 cuộc gọi đến (Em dùng call_kit_comming) để wake app lên. Nhưng khi ấn vào accept cuộc gọi thì vào app -> reconnect socket nhưng ko bắt lại được cuộc gọi đến. Cái này xử lý kiểu gì nhỉ anh. Anh làm rồi cho em tham khảo ý kiến với