Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Set OpenSSL MTU to avoid Edge "DTLS handshake failed" #217

Merged
merged 1 commit into from
Oct 11, 2018

Conversation

michaelfig
Copy link
Contributor

@michaelfig michaelfig commented Oct 11, 2018

Quick-and-dirty way to get Edge to be able to negotiate DTLS successfully. Otherwise it fails with:

ORTC18615: ORTC RTCDtlsTransport: DTLS handshake failed. hr=c004e00f.

See: https://mta.openssl.org/pipermail/openssl-users/2015-June/001506.html for OpenSSL implementation information. We could implement a BIO filter, but can't crib the code from Janus because it's GPLv3.

I still don't have Edge working in my project, but at least it doesn't give an error anymore.

Thanks,
Michael.

Quick-and-dirty way to get Edge to be able to negotiate DTLS successfully.

See: https://mta.openssl.org/pipermail/openssl-users/2015-June/001506.html for information.
@michaelfig
Copy link
Contributor Author

Correction: I can stream from Edge's getUserMedia to other browsers, but not with video.captureStream() (which is what I'd expect... Edge doesn't support it). Still can't get Edge to display a stream from itself or other browsers, even with the DTLS issue solved.

@michaelfig michaelfig changed the title Set MTU on DTLS to avoid Edge "DTLS handshake failed" Set OpenSSL MTU to avoid Edge "DTLS handshake failed" Oct 11, 2018
@ibc
Copy link
Member

ibc commented Oct 11, 2018

Thanks. I cannot yet test Edge (no Windows machine), however I've been able to test Edge using an online service and indeed I get DTLS handshake failed. hr=c004e00f.

Some questions:

@ibc
Copy link
Member

ibc commented Oct 11, 2018

Regarding the Edge issue related to received media (Consumer), please check #192 and comment there. I think it may be 100% related.

@michaelfig
Copy link
Contributor Author

Yes, you are right. I don't know why I didn't search the issues (I thought I had)... was looking in the source code for mtu, but didn't find it.

Okay, great.

  • Why MTU 1200? Isn't it too small? I do know that Chrome/libwebrtc internally assumes MTU 1200 for WebRTC media, but wouldn't 1350 work as well? Have you tested it?

I just used what Janus did for the magic number. 1350 works fine, in my testing.

@ibc ibc merged commit 3d5bc02 into versatica:master Oct 11, 2018
@ibc
Copy link
Member

ibc commented Oct 11, 2018

mediasoup 2.2.4 released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants