Open endurable-remodeler-eleven opened 5 years ago
jryans
commented
5 years ago Thanks for the report!
What happens if you try other WebRTC based apps using the same network connection as the one having the issue?
For example, you could try https://appr.tc/ or https://appear.in/.
(I am just trying to isolate if you see the same for any WebRTC based call, or Riot only.)
Player701
commented
5 years ago Same bug here. Both sides receive the "could not connect media" error. There seems to be a problem connecting via https://appr.tc/ as well. No LAN / VPN used.
Permissions for the web app to access web camera and microphone have been granted.
Firefox 66.0.3, Windows 10, riot.im/app
SimonBrandner
commented
3 years ago Then this seems to be an upstream issue, sorry.
an0o0nym
commented
2 years ago Hi, I have the same issue as described above. Can anyone help to debug this problem? When calling people that are on the LAN it works fine. When I try cal someone from outside the LAN it fails with "could not connect media" error.
Thats what I get in my firefox console:
Discarding an event, we don't have a call/peerConn m.room.encrypted rageshake.ts:60:15
Hangup received for call ID xxxxxxxxxxx rageshake.ts:60:15
stopAllMedia (stream=[object MediaStream]) rageshake.ts:60:15
Stopping usermedia stream {cbd342de-13d6-42e5-9c2d-77bd3533182a} rageshake.ts:60:15
Splicing usermedia stream out stream array {cbd342de-13d6-42e5-9c2d-77bd3533182a} rageshake.ts:60:15
Call state in !xxxxxxxxxxx:mydomain.com changed to ended rageshake.ts:60:15
Removing call for room !xxxxxxxxxxx:mydomain.com rageshake.ts:60:15
Call completed. Call ID: xxxxxxxxxxx, virtual room ID: !xxxxxxxxxxx:mydomain.com, user-facing room ID: !xxxxxxxxxxx:mydomain.com, direction: outbound, our Party ID: xxxxxxxxxxx, hangup party: remote, hangup reason: ice_failed rageshake.ts:60:15
Local candidates: rageshake.ts:60:15
c2915d08 - type: host, address: 172.X.X.X, port: 49427, protocol: udp, relay protocol: undefined, network type: undefined rageshake.ts:60:15
f5eb7160 - type: host, address: 172.X.X.X, port: 43067, protocol: udp, relay protocol: undefined, network type: undefined rageshake.ts:60:15
3e83c1a6 - type: host, address: 172.X.X.X, port: 55588, protocol: udp, relay protocol: undefined, network type: undefined rageshake.ts:60:15
935cbc5f - type: host, address: 172.X.X.X, port: 53342, protocol: udp, relay protocol: undefined, network type: undefined rageshake.ts:60:15
53e5b6a3 - type: host, address: 172.X.X.X, port: 51589, protocol: tcp, relay protocol: undefined, network type: undefined rageshake.ts:60:15
c6568990 - type: host, address: 172.X.X.X, port: 58960, protocol: tcp, relay protocol: undefined, network type: undefined rageshake.ts:60:15
c887fa2f - type: host, address: 172.X.X.X, port: 64363, protocol: tcp, relay protocol: undefined, network type: undefined rageshake.ts:60:15
770da316 - type: host, address: 172.X.X.X, port: 61465, protocol: tcp, relay protocol: undefined, network type: undefined rageshake.ts:60:15
Remote candidates: rageshake.ts:60:15
dfab9812 - type: host, address: 10.X.X.X, port: 60294, protocol: udp rageshake.ts:60:15
ef0f89b5 - type: host, address: 10.X.X.X, port: 9, protocol: tcp rageshake.ts:60:15
Candidate pairs: rageshake.ts:60:15
935cbc5f / dfab9812 - state: inprogress, nominated: false, requests sent undefined, requests received undefined, responses received: undefined, responses sent: undefined, bytes received: 0, bytes sent: 0, rageshake.ts:60:15
3e83c1a6 / dfab9812 - state: inprogress, nominated: false, requests sent undefined, requests received undefined, responses received: undefined, responses sent: undefined, bytes received: 0, bytes sent: 0, rageshake.ts:60:15
f5eb7160 / dfab9812 - state: inprogress, nominated: false, requests sent undefined, requests received undefined, responses received: undefined, responses sent: undefined, bytes received: 0, bytes sent: 0, rageshake.ts:60:15
c2915d08 / dfab9812 - state: inprogress, nominated: false, requests sent undefined, requests received undefined, responses received: undefined, responses sent: undefined, bytes received: 0, bytes sent: 0, rageshake.ts:60:15
Presence: unavailable rageshake.ts:60:15
Description
When trying to make a voice call I cannot connect to the other person. The call tries to connect then says "User ended the call. (could not connect media)". This is across the internet, not LAN. If I connect to personal VPN from outside LAN, I can hear the other person who is inside the LAN but they cannot hear me.
Steps to reproduce
Describe how what happens differs from what you expected.
Log: sent
Version information
For the web app:
For the desktop app: