Voice and Video Calls to device on different network not working
-
so, i set up matrix synapse. chat room, messages all working. But when i try a 1 on 1 video call - *it works when both devices on same network(same home wifi). But when i try when one device is connected to a different network no success. Its stays at the connecting screen. I even opened all ports to all protocol in my vps's vnc subnet ( i am using oracle ubuntu instance - no firewall in ubuntu). What am i missing. I have been at it for more than two days. I thought the problem was with cloudflare and hence switched back to my domain providers dns NS. (haven't done federation yet) both chats are verified.
-
so, i set up matrix synapse. chat room, messages all working. But when i try a 1 on 1 video call - *it works when both devices on same network(same home wifi). But when i try when one device is connected to a different network no success. Its stays at the connecting screen. I even opened all ports to all protocol in my vps's vnc subnet ( i am using oracle ubuntu instance - no firewall in ubuntu). What am i missing. I have been at it for more than two days. I thought the problem was with cloudflare and hence switched back to my domain providers dns NS. (haven't done federation yet) both chats are verified.
In Firefox you got about:webrtc where you can check webRTC connections for errors.
Maybe check that and send the log and screenshots.Also in about:config you can set
media.peerconnection.ice.relay_onlytotrueto force the usage of the turn server. -
In Firefox you got about:webrtc where you can check webRTC connections for errors.
Maybe check that and send the log and screenshots.Also in about:config you can set
media.peerconnection.ice.relay_onlytotrueto force the usage of the turn server.@brutalbirdie so it doesn't concern about my server setup ?
-
@karthiceaswar can you see any hints about webrtc/ICE in the app logs or browser console logs?
I assume something does not work with connection negotiation.@nebulon How do i see it ?
-
In Firefox you got about:webrtc where you can check webRTC connections for errors.
Maybe check that and send the log and screenshots.Also in about:config you can set
media.peerconnection.ice.relay_onlytotrueto force the usage of the turn server.@brutalbirdie my about:webrtc logs
I couldn't make any of it.
-
@brutalbirdie my about:webrtc logs
I couldn't make any of it.
@karthiceaswar from the logs it looks like it is unable to find a direct connection between the two clients for webrtc. In such a case it should fallback to using the turn server for relay but also that doesn't seem to work out.
The turn server requires your firewall to be open for connections at 3478,5349 (udp and tcp) and a whole port range from 50000 to 51000 (udp)
Maybe that is the issue?
-
@karthiceaswar from the logs it looks like it is unable to find a direct connection between the two clients for webrtc. In such a case it should fallback to using the turn server for relay but also that doesn't seem to work out.
The turn server requires your firewall to be open for connections at 3478,5349 (udp and tcp) and a whole port range from 50000 to 51000 (udp)
Maybe that is the issue?
@nebulon as for the firewall in my server i have opened up all ports and connection. Those ports are already open. Do I need to set port rule in Docker (is it actually possible) ?! This is my security list for the vnc rule.
-
@nebulon as for the firewall in my server i have opened up all ports and connection. Those ports are already open. Do I need to set port rule in Docker (is it actually possible) ?! This is my security list for the vnc rule.
@karthiceaswar Cloudron manages the server local firewall (iptables and docker rules) automatically, so you don't have to tweak the firewall of the server itself. I was more referring to any potential external firewall, but as you've mentioned this is all open as well.
To be honest, those webrtc issues are always hard to debug
Have you tried to reach out to the upstream element developer community as well?
-
@karthiceaswar Cloudron manages the server local firewall (iptables and docker rules) automatically, so you don't have to tweak the firewall of the server itself. I was more referring to any potential external firewall, but as you've mentioned this is all open as well.
To be honest, those webrtc issues are always hard to debug
Have you tried to reach out to the upstream element developer community as well?
@nebulon Nope. I tried with different client too. But no success. Man....Its a bummer. I really need that 1 to 1 Video and audio calls to work. I even purged netfilter-persistent iptables-persistent. No success. It only works on same network. Anyway thanks for the effort.
