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

Reconnection issue with two devices #6

Closed
avastou opened this issue Jan 7, 2014 · 6 comments
Closed

Reconnection issue with two devices #6

avastou opened this issue Jan 7, 2014 · 6 comments

Comments

@avastou
Copy link

avastou commented Jan 7, 2014

Hi,
I have this issue when simulate reconnection device (by refresh the html page):

rtc/couple error (createAnswer):  SetLocalDescription failed: Failed to push down answer transport description. 

For information, one of my device, no have webcam (but audio), Do you have some idea ?

@DamonOehlman
Copy link
Member

I have seen that same situation in my own testing. I'm going to be working on reliably recreating the error today and then implementing a fix. From: avastouSent: Wednesday, 8 January 2014 8:54 AMTo: rtc-io/rtc-quickconnectReply To: rtc-io/rtc-quickconnectSubject: [rtc-quickconnect] Reconnection issue with two devices (#6)Hi,
I have this issue when simulate reconnection device (by refresh the html page):

rtc/couple error (createAnswer): SetLocalDescription failed: Failed to push down answer transport description.

For information, one of my device, no have webcam (but audio), Do you have some idea ?

—Reply to this email directly or view it on GitHub.

@DamonOehlman
Copy link
Member

So the good news is that I'm able to recreate the issue reliably - looking into what is required to resolve the problem now.

@DamonOehlman
Copy link
Member

I'd be interested to know whether reinstalling the rtc-quickconnect module will fix this problem for you. Reinstalling will bring in rtc@0.13.5 in which I have seen the test case I managed to recreate with a similar problem disappear.

@DamonOehlman
Copy link
Member

If this still does occur, then I believe it will be the result of rtc-io/rtc#14 which I am attempting to get to the bottom of now.

@DamonOehlman
Copy link
Member

If this is still causing you problems, I'd recommend looking at the conferencing example in the examples/ folder. For the moment, based on the issues that browsers have with renegotiation (chrome occasionally gets stuck, and firefox flat out refuses) I'm opting for more preparation before attempting connection (i.e capture a media stream prior to announcing in the room).

I've just published rtc-quickconnect@0.8.3 which assumes a non-reactive approach to avoid similar issues until the browsers resolve the renegotiation issues..

@avastou
Copy link
Author

avastou commented Jan 23, 2014

thanks!

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

No branches or pull requests

2 participants