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.

Sign up for GitHub

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

Jump to bottom

Cannot establish VOIP connection between two different matrix servers #18650

Closed
Palid opened this issue Aug 20, 2021 · 5 comments
Closed

Cannot establish VOIP connection between two different matrix servers #18650

Palid opened this issue Aug 20, 2021 · 5 comments
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Investigation Z-Rageshake Has attached rageshake (not for log submission process)

Comments

@Palid
Copy link
Contributor

Palid commented Aug 20, 2021

This could probably be split into couple of smaller issues, but I'd prefer someone more involved in VOIP to first have a look at this.
It seems that there's a few different problems here.

First one is that for some reason I couldn't establish VOIP connection neither within matrix.hackerspace.pl <->matrix.hackerspace.pl server, nor matrix.org <-> matrix.hackerspace.pl

The second one is that in case of not being able to establish a connection due to this error (missing config on synapse? turn server? no idea so far) we're not showing any indication of that to in the client, which may make the end-user think that the feature's just broken for no particular reason. Showing that it can't establish connection because it's not supported or something similar would be a much better experience.
@SimonBrandner SimonBrandner added O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Investigation labels Aug 20, 2021
@SimonBrandner
Copy link
Contributor

@Palid, could you please send your logs, I think we can't do much without them

@SimonBrandner SimonBrandner added the X-Needs-Info This issue is blocked awaiting information from the reporter label Aug 20, 2021
@Palid
Copy link
Contributor Author

Palid commented Aug 20, 2021

@Palid, could you please send your logs, I think we can't do much without them

rageshake was sent, just trying to add another two ones.

@SimonBrandner SimonBrandner added Z-Rageshake Has attached rageshake (not for log submission process) and removed X-Needs-Info This issue is blocked awaiting information from the reporter labels Aug 20, 2021
@jeena
Copy link

jeena commented Mar 5, 2022

I have something similar but with a twist. I have two users on the same server. As long as they are in the same WiFi then it works just fine, but as soon as we are in different networks I get the same behavior.

@t3chguy
Copy link
Member

t3chguy commented Mar 8, 2022

@jeena sounds like your TURN server isn't working.

@t3chguy
Copy link
Member

t3chguy commented Nov 25, 2024

Closing as presumed TURN server misconfiguration, no response to dig deeper

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Investigation Z-Rageshake Has attached rageshake (not for log submission process)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jeena @t3chguy @Palid @SimonBrandner