The "options" in "peer.call(id, stream, options) " should be documented.

I saw the #126 before, but i think there is something meaningful in the peerconnection’s options. Because some problem confuses me when i tried to call the other peer with the audio only, i cannot received the video from that peer. After I search the google, I found that this situation happened because I don’t set the OfferToReceiveVideo to true, in webrtc constraints, it means if a caller only has the audio stream, the OfferToReceiveVideo is setting to false, even if the the callee answer a video stream, we won’t received it.

As soon as I set it like this:

    var options = {
        'constraints': {
            'mandatory': {
                'OfferToReceiveAudio': true,
                'OfferToReceiveVideo': true
            }
        }
    }
    var call = peer.call(otherPeer, callStream, options);

It finally works.

So I suggest that maybe we could document it in the Docs, or just set it as the default in the source code.

[TomaszRzucidlo]

    var constraints = {
        'mandatory': {
            'OfferToReceiveAudio': true,
            'OfferToReceiveVideo': true
        },
        offerToReceiveAudio: 1,
        offerToReceiveVideo: 1,
    }

You shoud name your object like “constraints” and then: var call = peer.call(otherPeer, callStream, constraints);

[Redmega]

@afrokick Do you have an example of using RTCRtpTransceiver for this? I’m confused as to how it would be implemented with Peer.JS. I’m having a fairly common issue – Users with video disabled should still be able to participate – but when I connect that media stream, the users who only have audio can also only recieve audio.