Open saoron opened 2 years ago
We have the same problem. I have set up the TURN server in the config.json and in our web application. When i check chrome://webrtc-internals/ during the setup-process i see the local and remote candidates of the relay, howewer the state of the candidate-pair remains 'in progress'. It seems there are no requestsReceived and responsesReceived. This i can also see in Whireshark: the web-app sends requests but nothing is sent back from the TURN server. The same web-app also uses WebRTC for voice (sipjs and Asterisk in the backend) and there requestsReceived and responsesReceived are rising. In Whireshark i see Data Indications from the TURN server as well as Channel-Bind (which doesnt happen with RTSPtoWeb) and a connection is made (thats why i think, the problem is not in the web-app and not in the TURN server). I also see the remote candidates of RTSPtoWeb are slightly different than those of Asterisk, but i dont really know, if that is a problem. I'm suspecting, the problem could be in the underlying Pion WebRTC or in the part how it is used, but im currently missing the capabilities to debug that efficiently. Maybe someone could help or point me in the right direction. I would be happy to do further tests or help with anything, if i can.
Check this, https://github.com/flutter-webrtc/flutter-webrtc/issues/758#issuecomment-1032430208
it works on my side by a coturn server.
Thanks very much for your reply. Indeed if I set up my own Coturn and uncomment 'server-relay' line, it works. Now in the Cotrurn wiki (https://github.com/coturn/coturn/wiki/turnserver), is written with capital and bold letters, that this should not be uncommented, which alerts me a little. This also kind of explains abit, why it didn't work in all the TURN servers I tried before. Could you explain to me, why this setting is needed or is there even a possibility to avoid it? I tested a slightly altered example from Pion (https://github.com/pion/webrtc/tree/master/examples/rtp-to-webrtc) which seems similar to what RTSPtoWeb is doing on the WebRTC side (I just had to add the TURN settings on both ends and the 'iceTransportPolicy': 'relay' in the jsfiddle) and interestingly, this also works without uncommenting 'server-relay'. However i couldnt find out yet, where the differences are.
Thanks very much for your reply. Indeed if I set up my own Coturn and uncomment 'server-relay' line, it works. Now in the Cotrurn wiki (https://github.com/coturn/coturn/wiki/turnserver), is written with capital and bold letters, that this should not be uncommented, which alerts me a little. This also kind of explains abit, why it didn't work in all the TURN servers I tried before. Could you explain to me, why this setting is needed or is there even a possibility to avoid it? I tested a slightly altered example from Pion (https://github.com/pion/webrtc/tree/master/examples/rtp-to-webrtc) which seems similar to what RTSPtoWeb is doing on the WebRTC side (I just had to add the TURN settings on both ends and the 'iceTransportPolicy': 'relay' in the jsfiddle) and interestingly, this also works without uncommenting 'server-relay'. However i couldnt find out yet, where the differences are.
Wondering the same here, does anyone have an explanation?
Thank you for this plugin, My question is regarding an additional TURN server, After I set the credentials of an external TURN server it's not playing.
Any advice or example would be greatly appreciated.