linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Linphone-developers] Default reconnecting behavior


From: Sean Oh
Subject: [Linphone-developers] Default reconnecting behavior
Date: Thu, 29 Oct 2015 10:08:36 -0700

Hi,

I'm currently using Linphone library for Android development.

I wanted my app to be somewhat similar to 'Skype' when a user happen to have bad connection.


Background:
1. Using native latest Linphone Core Android SDK
2. Using Freeswitch SIP server


The scenario is like this.

1. A user having a phone call with linphone using WiFi connection
2. The router somehow got reset so the user lost connection, but Android OS (KitKat 4.4 in this case) switches the user to 4G network automatically, therefore user now has internet connection.

I emulated this scenario in the stock Linphone app from google play, and it seems to just throw away the phone call. I wanted the app to maintain the connection, but I know it's hard to copy and paste the same connection for different protocols. So I thought of this 'auto calling' feature.


Auto calling
1. A user having a phone call with linphone using WiFi connection
2. The router somehow got reset so the user lost connection, but Android OS (KitKat 4.4 in this case) switches the user to 4G network automatically, therefore user now has internet connection.
3. My app recognized the phone has been ended, but the user never triggered "End Phone Call" button, so it finds out the last phone number it contacted, and makes a phone call.


Problem:
When the switch has been made in relatively short time (< 3 seconds), the SIP server does not clear out the user instance quickly. Results in duplicate user instances. It prevents one user to not able to talk or listen to the phone call. 


Why does this happen and how should I handle this??

reply via email to

[Prev in Thread] Current Thread [Next in Thread]