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

Initiating calls from Chrome to OpenWebRTC can be unreliable #359

Open
superdump opened this issue Apr 24, 2015 · 10 comments
Open

Initiating calls from Chrome to OpenWebRTC can be unreliable #359

superdump opened this issue Apr 24, 2015 · 10 comments

Comments

@superdump
Copy link
Contributor

When trying to initiate a call from Chrome to any OpenWebRTC client (including NativeDemo on iOS) does not succeed to set up the connection.

@stefhak
Copy link
Contributor

stefhak commented Apr 24, 2015

Could you be more specific about app and versions? It works fine for me
Chrome 43.0.2357.37 beta (64-bit) to OWR on Mac OS X (but the build is not
totally fresh) and demo.openwebrtc.io.

On Fri, Apr 24, 2015 at 3:56 PM, Robert Swain notifications@github.com
wrote:

When trying to initiate a call from Chrome to any OpenWebRTC client
(including NativeDemo on iOS) does not succeed to set up the connection.


Reply to this email directly or view it on GitHub
#359.

@superdump
Copy link
Contributor Author

Hmm. It works fine for @Rugvip too. It seems like I get audio through but not video right now. Chrome stable (42.0.2311.90 64-bit on OS X) and any OWR application.

@superdump superdump changed the title Initiating calls from Chrome to OpenWebRTC is very unreliable Initiating calls from Chrome to OpenWebRTC can be unreliable Apr 24, 2015
@Khantareen
Copy link

khan

@stefhak
Copy link
Contributor

stefhak commented Apr 27, 2015

FWIW, I just did a clean build of OWR, and (I'm only testing video) Chrome <-> OWR works fine regardless of which one that initiates.

@WangHeng861021
Copy link

it seems that the DTLS in OpenWebRTC is disabled defaultly,so how to enable it in using OpenWebRtc,please give a hand for that.thanks a lot

@superdump
Copy link
Contributor Author

DTLS is a requirement for WebRTC, it is not disabled by default.

@marcin-sielski
Copy link

There are some problems with DTLS handshake. I have tried openwebrtc with the WebRTC gateway. Sometimes it succeeds only for audio channel. Sometimes it succeeds only for video channel. In some scenarios it succeeds all the time. OpenWebRTC does not responds to repeating dtls "hello" requests. Could you please let me know where to look at to track down this issue?

@stefhak
Copy link
Contributor

stefhak commented Sep 13, 2015

I suppose gstdtlsagent.c/h in gst-plugins-bad should be a starting point.

On Tue, Sep 8, 2015 at 12:24 PM, Marcin Sielski notifications@github.com
wrote:

There are some problems with DTLS handshake. I have tried openwebrtc with
the WebRTC gateway. Sometimes it succeeds only for audio channel. Sometimes
it succeeds only for video channel. In some scenarios it succeeds all the
time. OpenWebRTC does not responds to repeating dtls "hello" requests.
Could you please let me know where to look at to track down this issue?


Reply to this email directly or view it on GitHub
#359 (comment)
.

@Rugvip
Copy link
Contributor

Rugvip commented Sep 13, 2015

@marcin-sielski

If the DTLS client is repeatedly sending HELLO requests, and the server isn't receiving them, then it is most likely a problem lower down in the stack, namely ICE. If the server receives the messages but fails to respond, then it's probably a DTLS issue.

If you could take and upload a log of a failed call setup with a single media stream and GST_DEBUG=dtls:6 , I could have a look and see if it seems like a DTLS issue.

@bamboolsu
Copy link

Are there any updates for this issue?

Maybe this bug is related to #510.

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

No branches or pull requests

7 participants