Open co2nut opened 4 years ago
I am facing this same issue. Is there a way to resolve this?
Same issue
Same issue
Has anyone solved this?
Refer the document here. These examples are not currently support for srflx/relay candidate.
So STUN/TURN server cannot work for these example right now.
https://github.com/node-webrtc/node-webrtc-examples/blob/master/README.md
RTCPeerConnections are negotiated via REST API. The Server always offers (with host candidates) and the Client always answers. In order to negotiate a new RTCPeerConnection, the Client first POSTs to /connections. The Server responds with an RTCPeerConnection ID and SDP offer. Finally, the Client POSTs an SDP answer to the RTCPeerConnection's URL.
Client Server
| |
| POST /connections |
| |
|---------------------------------------------------->|
| |
| 200 OK |
| { "id": "$ID", "localDescription": "$SDP_OFFER" } |
| |
|<----------------------------------------------------|
| |
| POST /connections/$ID/remote-description |
| $SDP_ANSWER |
| |
|---------------------------------------------------->|
| |
| 200 OK |
| |
|<----------------------------------------------------|
Based on examples/record-audio-video-stream, when I run it on different network, it seems that it does not go through this listener
everything works fine on same network.
I tried to add below config too, but no luck
Is there anything that I could possibly miss out?