stun

问题 I am using ejabberd-16.04 on my mac and XMPPFramework from robbiehanson . It works fine for chatting, no problem. But now I want to add voice calling into my application. I am using Jingle Protocol for call establishment and it works fine for direct communication (i.e. both caller and callee are in same network). The problem I am facing is for cross-network and I want to implement Jingle ICE for this, NATed clients. 1 Can any one tell me how can I enable and use STUN/TURN module on ejabberd

问题 I've read that ICE is an agent on the WebRTC server which sends SDP information of users to STUN or TURN server. STUN and TURN server gives this SDP information and makes a P2P connection for the users. Is that true? So, what is the exact difference between STUN and TURN server? If the ICE agent configured with a TURN server, what would be happened with data flow? in this instance, TURN just act as a datagram-forwarder? 回答1: TURN is a relay — both clients send data to the TURN server, which

问题 I read RFC6577 and RFC8445 but I feel like there is a bit of a disconnect between how TURN can be used versus how ICE actually utilizes the relay candidates . The TURN RFC describes the use of one single TURN server to ferry data between a client and a peer. The transport address on the TURN server accepts data flow from a client via TURN messages, whereas the relayed transport address accepts data flow from peer(s) via UDP. This sounds great - one TURN server and bidirectional data flow.

问题 I read RFC6577 and RFC8445 but I feel like there is a bit of a disconnect between how TURN can be used versus how ICE actually utilizes the relay candidates . The TURN RFC describes the use of one single TURN server to ferry data between a client and a peer. The transport address on the TURN server accepts data flow from a client via TURN messages, whereas the relayed transport address accepts data flow from peer(s) via UDP. This sounds great - one TURN server and bidirectional data flow.

问题 I read RFC6577 and RFC8445 but I feel like there is a bit of a disconnect between how TURN can be used versus how ICE actually utilizes the relay candidates . The TURN RFC describes the use of one single TURN server to ferry data between a client and a peer. The transport address on the TURN server accepts data flow from a client via TURN messages, whereas the relayed transport address accepts data flow from peer(s) via UDP. This sounds great - one TURN server and bidirectional data flow.

来源： https://stackoverflow.com/questions/23434753/chrome-webrtc-datachannels-ice-tcp-server-reflexive-candidates-missing-even-wit

来源： https://stackoverflow.com/questions/23434753/chrome-webrtc-datachannels-ice-tcp-server-reflexive-candidates-missing-even-wit

问题 Is it possible to force a TCP tunneled (TLS) connection with WebRTC? We are developing a WebRTC application for our business, but we are experiencing some major issues with incoming UDP streams caused by our internal network. We are already using a TURN server and we are getting a bunch of ICE candidates (even relay UDP ones). The thing is, as I stated above, that our incoming UDP traffic does not work reliable here (stuttering, very bad image quality, very low fps). It's enough to give the

问题 If I am building a WebRTC app and using a Selective Forwarding Unit media server, does this mean that I will have no need for STUN / TURN servers? From what I understand, STUN servers are used for clients to discover their public IP / port, and TURN servers are used to relay data between clients when they are unable to connect directly to each other via STUN. My question is, if I deploy my SFU media server with a public address, does this eliminate the need for STUN and TURN servers? Since

问题 I am developing a P2P application, and I need to use STUN and/or TURN for NAT traversal. I have looked into the issues that an arise when using STUN only (basically it will not always work because it is UDP based and some firewalls won't like that - the reason is not that interesting as per my question), and I keep seeing recommendations about using STUN and TURN for fallback (the ICE scheme). But everywhere I look I just see people STUN as "unlikely to always work". What I am looking for is