Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Unable to record video from different network #37

Open
co2nut opened this issue Oct 29, 2020 · 5 comments
Open

Unable to record video from different network #37

co2nut opened this issue Oct 29, 2020 · 5 comments

Comments

@co2nut
Copy link

co2nut commented Oct 29, 2020

Based on examples/record-audio-video-stream,
when I run it on different network, it seems that it does not go through this listener

videoSink.addEventListener('frame', ({ frame: { width, height, data }}) => {

everything works fine on same network.

I tried to add below config too, but no luck

peerConnections = new RTCPeerConnection({
            sdpSemantics: 'unified-plan',
            iceServers: [
              {
                urls : 'stun:stun.l.google.com:19302'
              },
              {
                urls : 'turn:numb.viagenie.ca',
                username: "abc@hotmail.com",
                credential: "password",
              }
            ]
          }    
})

Is there anything that I could possibly miss out?

@Pirsanth
Copy link

I am facing this same issue. Is there a way to resolve this?

@kalradivyanshu
Copy link

Same issue

1 similar comment
@TurningTide
Copy link

Same issue

@brndusic
Copy link

brndusic commented Mar 1, 2021

Has anyone solved this?

@milochen0418
Copy link

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


RTCPeerConnection Negotiation

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  |
  |                                                     |
  |<----------------------------------------------------|

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants