-
Notifications
You must be signed in to change notification settings - Fork 497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VOIP Call on working on different network connection. #3059
Comments
I'm experiencing this issue too when calling from or being called on an Android device (on WiFi) to iOS device (on 4G). Might be related to element-hq/element-android#2255 |
I experience the same issue but sometimes it works but most of the times not. Element web or desktop with iOS works fine. The connection is not relevant in my case. Both WiFi or 4g or a combination of it keeps it the same. Desktop and web are both on a local ISP with utp connection. |
I have to correct my image. On my side it was a missing a good working coturn server. Once configured I have always a good and direct connection. From the synapse admin channel I also found this website to test your turn setup: https://test.voip.librepush.net/ |
I currently see similar issues although the turnserver is according to https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ working as expected. One thing I discovered is that the test seems to only do some basic connection tests. For more complete testing you need at least six clients, which means two of the following clients: client 1: ipv4 from a known server network range (because of server-relay option in coturn) Which results in at least into the following tests: client 2a <-> client1b client 3a <-> client1b Not knowing about the filters on coturn, there might be even the need to test whether clients behind a Carrier-grade NAT (RFC 6264) are working. The critical issue is that software such as element might not use the turn-server at all in case the clients are inside the same network or firewall hole-punching is working. Is there a more complete testing-service on the web? |
Scenario 1:
Calling between Device 1 and Device 2 works. Scenario 2:
Calling between Device 1 and Device 2 works. Scenario 3:
Synapse Server and Device 2 are under the same LAN, e.g. Server is 10.0.0.2, Device 2 is 10.0.0.5 Scenario 4:
Calling between Device 1 and Device 2 does not work. The App always show "Call Connecting..." Scenario 5:
Calling between Device 1 and Device 2 does not work. The App always show "Call Connecting..." Scenario 6:
Calling between Device 1 and Device 2 does not work. The App always show "Call Connecting..." Scenario 7:
Calling between Device 1 and Device 2 does not work. The App always show "Call Connecting..." More info:
I am using TURN server from https://www.metered.ca/tools/openrelay/ |
|
I had some free time today so I tried to spin up the server again. Here is the log from my own coturn server: Note that my private ip address range is 10.0.0.0/8, so I am not blocking those IPs specifically in my denied ip list. And
|
My coturn config (using valid zeroSSL cert):
|
We are facing issues in VOIP(Audio & Video) calls. Its working on same wifi network but always stuck in call connecting when switch to different network or 4G connection.
We have used the latest Matrix SDK in our project. Please support us to resolve this issue.
The text was updated successfully, but these errors were encountered: