Android client gets disconnected from the call after switch from Mobile data to WiFi

[gab07]

Describe the bug Switching networks during a call will disconnect the user from the call.

To Reproduce

• Use the basic video chat example
• Use a device with mobile data and wifi
• Once connected to the call using mobile data, switch to use wifi

Expected behavior Android client should be able to reconnect to the call after switching networks.

Device (please compete the following information):

• Android SDK version: 2.22.0
• OS and version: Android 11

[v-kpheng]

Thanks, @gab07, for filing this issue.

Are you able to reproduce using the latest version of the SDK?

[gab07]

I just reproduced it usingv2.23.1. I've found this article and after reading it I'm not sure if this is a bug or intended behavior.

[v-kpheng]

Thanks, @gab07. I think the article is outdated. I'll look into getting it updated 🤞.

In any case, switching from cellular to WiFi should work.

[v-kpheng]

https://jira.vonage.com/browse/OPENTOK-49285

[goncalocostamendes]

@gab07 just tried it out in our latest version v2.25.3 and the app automatically reconnects when switching networks. Can you tried it out? In case automatically network handover is not successful, does your app crashes or the client just disconnects from the session and you are required to join the session again?

[gab07]

@goncalocostamendes Hey, I re-tested this issue using the Basic-Video-Chat-Kotlin example from this repo and I've found that after switching from Data to WiFi:

• The mobile client square hangs for like 6 seconds
• Then it works well for a few seconds
• Then the mobile square disappears (from web)
• Then the app says "The connection to the OpenTok messaging server was dropped. Check the network connection."
• And then the app closes itself.

Notes:

• Web square (or feed) works the whole time.
• This only happens when you switch from Data to WiFi not the other way around.
• I'm using an Android phone and the Video API Playground

Answering your question, the mobile client doesn't crash but it is required to rejoin because it gets disconnected from the call.

[goncalocostamendes]

Hi @gab07! I have tried to reproduce your Use Case, but without success. Both with relayed and routed sessions.

The behaviour you describe is consistent with tipical publisher timeout after stream dropped. The timeout is always 15 seconds after network is disconnected.

Our network reconnection logic provides some logs if enabled that can provide us some insights on why the publisher is disconnecting. Would it be possible for you to enable advanced logging (with the following code) to the log file and provide it?

override fun onCreate(savedInstanceState: Bundle?) {
        ...
        com.opentok.android.OpenTokConfig.setJNILogs(true);
        com.opentok.android.OpenTokConfig.setOTKitLogs(true);
        com.opentok.android.OpenTokConfig.setWebRTCLogs(true);
    }

[gab07]

These are the logs that I've got. There were a lot of text, I'm not sure if I've got it right.

logs.txt

[goncalocostamendes]

@gab07 I had a change to look into the logs. Was this the full log file? I ask because the logs only report 11 seconds of the session, but I can see the session was much longer.

However it is possible to see that the session was not able to connect in a bit more of 10s (timeout should be 15s) triggering session destruction without a clear reason so there is definitely more digging to do.

Could you share the entire logs? Also, if possible, attaching a video of the issue occuring would be ideal.