Video one-way broadcasting not working

[diorray]

No description provided.

[muaz-khan]

Seems NAT traversing issue. One-Way broadcasting experiment is using RTCPeerConnection-v1.5.js library. From line 13 to 34, you can see that I'm using three ICE servers: one STUN server and two TURN servers.

You should remove all these lines and use following TURN server as the only ICE server:

iceServers = {
    iceServers: [{
            url: 'turn:webrtc%[email protected]',
            credential: 'muazkh'
        }
    ]
};

If this TURN address fails; try to use your custom TURN server.

Note: Test one-way video broadcasting experiment again; it must work!

[muaz-khan]

I suggest you try RTCWeb APIs directly instead of using any wrapper library. It is easy and will be a fun!

You can install/write your own custom TURN server; there are many public service providers too. All active/new TURN servers seem working.

TURN is suggested because it can easily traverse symmetric NATs.

In your scenario; you want to broadcast your video over about 100-peers. You need to install/program a media-server to handle such kind of broadcasting job. I.e. you should implement MCU model commonly known as peer-to-server model.

FYI, in peer-to-peer scenario, currently maximum 10 peers can be connected on chrome; also performance and quality issues are obvious cases in such model.

Developers already built WebSockets apps in PHP; it will be faster signaling method comparing HTTP-requests (i.e. XHR) based signaling.