Network / TURN server question about the JS SDK

[Albin]

I'm building a web application which is intended to work as a teams meeting / google meet application but with additional / custom functionality.

I'm developing it with React and I'm using the Javascript SDK (WebRTCAdaptor) following examples.

Some customers though cannot stream or receive streams, it's completely blank for them and they get a publishingTimeoutError. 

I've reached out to support and they gave me a TURN server to use, which was supposed to solve the issue but it didn't. 

 

MS Teams & Google Meet works for the customer so in theory it should't be a problem to get this working. They have strict firewall rules which is likely causing the issue.

I tried adding the TURN server in the peerconnection_config. Is there an issue with the way I'm adding it?

peerconnection_config: {

        iceServers: [

          { urls: 'turn:123.123.123.123:3478', username: 'abc123', credential: 'abc123' },

        ],

      },

I installed Wireshark and analyzed the traffic both in a teams meeting and in an ant media conference call,

and i noticed that when in a teams meeting traffic flowed like: port 50000 client 1 <-> 3480 turn server <->50000 client 2

and when in an ant media conf call with TURN server configured: src port 65000 dest port 50000 client 1 <-> ant media server <-> src port 50000 dest port 65000

 

Is there something i've configured wrong? shouldn't traffic flow from client 1 to client 2 with WebRTC without going through the ant media server?
 

[Albin]

I might have solved it, will know when they have tested it.

I found an option for the peerconfig: 

iceTransportPolicy: 'relay',

Now the wireshark traffic looks pretty much exactly like it does when in a teams meeting.

[Albin]

12 minutes ago, Albin said:

I might have solved it, will know when they have tested it.

I found an option for the peerconfig: 

iceTransportPolicy: 'relay',

Now the wireshark traffic looks pretty much exactly like it does when in a teams meeting.

Update: It did not seem to work.

In wireshark i see however that when in an ant meeting all packets are sent using the STUN protocol to port 3478,

But in a teams meeting they are sent using UDP protocol to port 3480

[Albin]

2 hours ago, Albin said:

Update: It did not seem to work.

In wireshark i see however that when in an ant meeting all packets are sent using the STUN protocol to port 3478,

But in a teams meeting they are sent using UDP protocol to port 3480

I will now try and use port 443 for the TURN server and see if that works.