Intermittent Connectivity Issues and Delayed Audio with COTURN Server in Android App

[SujithManjavana]

I've set up a COTURN server for my Android app that utilizes peer.js for webRTC voice communication. While testing with the TURN server URL using https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/, there are no apparent issues. However, in the actual application, I'm encountering intermittent connectivity problems.

Specifically, when Person A initiates a call to Person B, most of the time, the call fails with neither party being able to hear anything. Strangely, if Person B initiates the call to Person A, it consistently works without any issues. Additionally, in successful calls, the initial voice only homes after a 3-6 seconds delay.

Here are some details about the setup:

• Both clients (Person A and Person B) are connected to Wi-Fi networks.
• The COTURN server is running on a server with 1GB RAM and a single-core shared CPU. (Currently, my app has only less than 2k active users.)
• Client setup - PeerJS running on android webview.
• Firewall rules have been configured to allow traffic on ports 443 and 3478.

I've reviewed the network configuration, ensured correct TURN server implementation in the Android app, and monitored server resources without finding a resolution.

Could you please provide guidance on how to troubleshoot and resolve this issue? Any insights or suggestions would be greatly appreciated.

Thank you!

[jonesmz]

You'll need to perform a wireshark capture on both client devices, and read the logs of their ICE negotiations, to fully understand what is happening.