Skip to content
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

Could not connect media #9433

Open
endurable-remodeler-eleven opened this issue Apr 12, 2019 · 4 comments
Open

Could not connect media #9433

endurable-remodeler-eleven opened this issue Apr 12, 2019 · 4 comments

Comments

@endurable-remodeler-eleven

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

  • Make a voice call from outside the LAN

Describe how what happens differs from what you expected.

Log: sent

Version information

  • Platform: web (Firefox), desktop, and android via f-droid?

For the web app:

  • Browser: Firefox 66.0.3
  • OS: Windows 10
  • URL: riot.im/app

For the desktop app:

  • OS: Windows 10
  • Version: 1.0.7
@jryans
Copy link
Collaborator

jryans commented Apr 12, 2019

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.)

@jryans jryans added the X-Needs-Info This issue is blocked awaiting information from the reporter label Apr 12, 2019
@Player701
Copy link

Player701 commented May 1, 2019

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
Copy link
Contributor

Then this seems to be an upstream issue, sorry.

@SimonBrandner SimonBrandner added Z-Upstream and removed P1 X-Needs-Info This issue is blocked awaiting information from the reporter labels Jul 30, 2021
@an0o0nym
Copy link

an0o0nym commented Dec 29, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants