Turn TCP/UDP #73

New Issue

Closed

opened 2021-10-04 13:50:46 +00:00 by timowevel1 · 6 comments

timowevel1 commented

2021-10-04 13:50:46 +00:00

(Migrated from github.com)

Hey,

why is tcp disabled in the turn config but used in the prosody config?

Thanks!

Hey, why is tcp disabled in the turn config but used in the prosody config? Thanks!

Ark74 commented

2021-10-04 14:01:28 +00:00

(Migrated from github.com)

What line?

timowevel1 commented

2021-10-04 14:02:17 +00:00

(Migrated from github.com)

no-tcp in turnserver.conf
and using tcp on 5349 for turns in the prosody conf

{ type = "turns", host = "jitsidev.facilisglobal.com", port = 5349, transport = "tcp", secret = true, ttl = 86400, algorithm = "turn" }

no-tcp in turnserver.conf and using tcp on 5349 for turns in the prosody conf { type = "turns", host = "jitsidev.facilisglobal.com", port = 5349, transport = "tcp", secret = true, ttl = 86400, algorithm = "turn" }

Ark74 commented

2021-10-04 14:08:01 +00:00

(Migrated from github.com)

I mean in the installer.

IIRC we don't touch that line, that should come from the jitsi package configuration itself, if you have being updating from back in time, it might be possible at the time that part was not enabled, but recent versions do, ~~sadly~~ some files become static, so no further changes are applied, like ngxin conf, domain.com-config.js, etc. So the maintainer needs to update/fix those.

Please confirm.

I mean in the installer. IIRC we don't touch that line, that should come from the jitsi package configuration itself, if you have being updating from back in time, it might be possible at the time that part was not enabled, but recent versions do, <strike>sadly</strike> some files become static, so no further changes are applied, like ngxin conf, domain.com-config.js, etc. So the maintainer needs to update/fix those. Please confirm.

timowevel1 commented

2021-10-04 14:10:30 +00:00

(Migrated from github.com)

Dont quite understand, what should I confirm? So I should just leave it as it is?

Ark74 commented

2021-10-04 14:22:15 +00:00

(Migrated from github.com)

Dont quite understand, what should I confirm?

If we tainted that particular line of configuration with the installer.

So I should just leave it as it is?

That depends on what you try to accomplish, AFAICT that's the default installation value and it works for us, I see no reason to hard code it one way or another.

> Dont quite understand, what should I confirm? If we tainted that particular line of configuration with the installer. > So I should just leave it as it is? That depends on what you try to accomplish, AFAICT that's the default installation value and it works for us, I see no reason to hard code it one way or another.

timowevel1 commented

2021-10-04 16:32:12 +00:00

(Migrated from github.com)

Okay then I will just leave it as it is, thank you!