Skip to content
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.

STUN or TURN setup need ? #1358

Open
Dav151 opened this issue Nov 23, 2023 · 2 comments
Open

STUN or TURN setup need ? #1358

Dav151 opened this issue Nov 23, 2023 · 2 comments

Comments

@Dav151
Copy link

Dav151 commented Nov 23, 2023

Hi ,

  1. Do we need to setup the STUN or TURN serve in the MCU ?
  2. Or the MCU already have a default one ? so that even clients behind the firewall can connect to the MCU, and do forward mode or mixed mode publish and subscribe ?

As i see in owt/webrtc_agent/agent.toml, it has the config as below:

#STUN server IP address and port to be used by the server.
#if "" is used, the address is discovered locally
stunport = 0 #default: 0
stunserver = "" #default: ""

and in /webrtc_agent/webrtc/connection.js, the program only check STUN server and ignore TURN server. why?

_createWrtc() {
var wrtc = new addon.WebRtcConnection(
this.threadPool, this.ioThreadPool, this.id,
global.config.webrtc.stunserver,
global.config.webrtc.stunport,
global.config.webrtc.minport,
global.config.webrtc.maxport,
false, //this.trickleIce,
this._getMediaConfiguration(this.mediaConfiguration),
false,
'', // turnserver,
'', // turnport,
'', //turnusername,
'', //turnpass,
'', //networkinterface
this.ipAddresses
);

return wrtc;

}

Can any one help to answer? Thanks

@raviprakashsrivastava
Copy link

You need to add a stun server address. Google stun servers are good to go with.

@Dav151
Copy link
Author

Dav151 commented Dec 8, 2023

ok, Thanks for the reply.

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

No branches or pull requests

2 participants