search

otalk / rtcpeerconnection-shim

Implementation of the RTCPeerConnection API ontop of ORTC
BSD 3-Clause "New" or "Revised" License
15 stars 14 forks source link

Edge remote dtls parameters seems to have a hardcoded role of client. #173

Open k-raynov opened 5 years ago

k-raynov commented 5 years ago

Hello,

We are using rtcpeerconnection-shim for RTCPeerConnections with Edge. Here's what we have as an offer/answer scenario: 

1) Edge sending a SDP offer with `a=setup:actpass`
2) Edge getting a SDP answer with `a=setup:passive`
3) This results in both peers staying passive so no DTLS handshake is initiated.

It all boils down to this line and it seems that remote dtls parameters role is hardcoded to client while it should be read from the sdp a=setup:... lines ? https://github.com/otalk/rtcpeerconnection-shim/blob/master/rtcpeerconnection.js#L870

Please advice if this is an issue or an intended behaviour ?