I am creating a serverless webRTC connection therefore I manually relay SDP info between two machines. If the response SDP is not given within a very short period of time after the offer SDP, the connection fails/times out. Is there a way to extend the amount of time between offering an SDP and ICE/RTC timeout? Is there another solution or workaround for this? Thanks!
Asked
Active
Viewed 1,303 times
2
-
What do you mean "very short"? I have no trouble [cut'n'pasting offers and answers](https://stackoverflow.com/a/29056385/918910) between machines, even if it takes several seconds. – jib Jan 13 '19 at 15:23
-
I waited 2 minutes before pasting the answer and it still worked. – jib Jan 14 '19 at 21:03
-
Check out this demo. https://owebio.github.io/serverless-webrtc-chat/ . In FF, status changes to 'failed' after clicking the Create button and waiting 10-15 seconds. Does not happen in Chrome apparently. – BSomo Jan 15 '19 at 05:59
-
Upgrade to Firefox 65 (out in 2 weeks). The 15 second ICE timeout appears to have been fixed there. Your demo wfm there even after waiting 20 minutes. – jib Jan 15 '19 at 20:29
-
Thanks jib! Solved. – BSomo Jan 15 '19 at 23:10
1 Answers
-1
More details from comments:
Check out this demo. owebio.github.io/serverless-webrtc-chat. In FF, status changes to 'failed' after clicking the Create button and waiting 10-15 seconds. Does not happen in Chrome apparently.
Upgrade to Firefox 65 (out in 2 weeks). The 15 second ICE timeout appears to have been fixed there. Your demo wfm there even after waiting 20 minutes.
jib
- 40,579
- 17
- 100
- 158