nat traversal - Is ICE Necessary for Client-Server WebRTC Applications? -


i have webrtc mcu (kurento) running on public ip address serving clients send or receive audio every clients directly connected mcu (not each other ) has public ip address .

q1: there still necessity use stun , turn nat traversal ?? if why ??
q2: there hack in webrtc in browser remove need stun , turn ?

in opinion : of client-server architectures not have difficulty clients behind nat .what's difference here webrtc?

yes ice absolutely must webrtc.

q1: there still necessity use stun , turn nat traversal ?? if why ??

for scenario don't need use stun or turn. let me explain why.

every client in private network under kind of nat has public ip address. outside world doesn't know client's private ip address , if knew can't connect client without knowing public ip address. stun server used gather public ip address.

so if server wants initiates connection needs client send nat's public ip. client use stun server know public ip , send server. if client initiates connection there no need know nat's public ip. client can send packets public server initiate connection. server can know cilents public ip clients packet , can connect. no need stun.

your server doing turn's role in scenario. don't need turn server.

q2: there hack in webrtc in browser remove need stun , turn ?

there no hack. depending on scenarios turn/stun used. scenario don't need. if wanted make client-client connection have needed stun server.


Comments

Popular posts from this blog

c# - Binding a comma separated list to a List<int> in asp.net web api -

Delphi 7 and decode UTF-8 base64 -

html - Is there any way to exclude a single element from the style? (Bootstrap) -