WebRTC Connection Negotiated only for some people

[Ambx-Kai]

Component your question relates to

• Signalling server
• Frontend library
• Frontend UI library
• Matchmaker
• SFU
• This repo
• Other

Background

I've setup a Pixel Streaming infrastructure on AWS, however there's a small portion of users which get stuck at this WebRTC Connection Negotiated.

Question

1. What would the main reason for this, is it due to connection is to a public STUN / TURN server?
2. Would the next steps to resolving the issue to look into setting up a STUN / TURN server on a separate AWS EC2?

[lukehb]

Can you share more details on:

I've setup a Pixel Streaming infrastructure on AWS

For instance, are you running a TURN server?

A1. Mostly commonly if some people can't connect it means they are behind a network that needs a TURN server.

A2. Yes. It is common to deploy a TURN server on a public IP address and configure the Pixel Streaming infrastructure to use that TURN ip when you start the signaling server. So you might do like start_with_stun.bat --turn xxx.xxx.xxx.xxx

You can see the args for configuring those batch scripes here:

PixelStreamingInfrastructure/SignallingWebServer/platform_scripts/cmd/common.bat

Line 22 in 13ce022

echo --turn ^<turn_ip^> TURN server to be used

You can then verify if the TURN server is working if you use the ForceTurn option in the settings panel of the frontend (which will discard non-TURN connections).

[Ambx-Kai]

Hey Luke, thanks for the reply.

Currently I am running this script:
SignallingWebServer/platform_scripts/bash/Start_WithTURN_SignallingServer.sh
branch 5.4

specifying only the --configFile param, from what I understood, by default this would spawn a TURN server alongside the SWS, are there potentially any ports that I would need to specifically open for it, which would mean users who need one would be stuck on the WebRTC Connection Negotiated since they can't establish a connection with the TURN server?

[lukehb]

which would mean users who need one would be stuck on the WebRTC Connection Negotiated since they can't establish a connection with the TURN server

Yep that sounds likely.

specifying only the --configFile param, from what I understood, by default this would spawn a TURN server alongside the SWS

Yep, that's correct. This setup is more for convenience to get you up and going rather than a suggestion of what should be done in production. For users to actually see that turn server then tcp and udp traffic need to be allowed for the port of the TURN server (19302 by default from memory or you can open all ports for a quick test that they can see it).

In practice, TURN server should be run on its own machine usually, with its own ports opened up.

[Ambx-Kai]

Just to comment back here, these are the ports I opened:
3478 TCP / UDP
49152-65535 TCP / UDP

[lukehb]

Just to comment back here, these are the ports I opened: 3478 TCP / UDP 49152-65535 TCP / UDP

@Ambx-Kai And it worked well for your purposes of connecting to a TURN server on AWS?

[Ambx-Kai]

Just to comment back here, these are the ports I opened: 3478 TCP / UDP 49152-65535 TCP / UDP

@Ambx-Kai And it worked well for your purposes of connecting to a TURN server on AWS?

Yep, it worked well for negating the issue mentioned in this issue, users who were encountering were being unable to connect to the TURN server, which opening those ports fixed the issue.