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!
2
votes
What do you mean "very short"? I have no trouble cut'n'pasting offers and answers between machines, even if it takes several seconds.
- jib
I waited 2 minutes before pasting the answer and it still worked.
- jib
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.
- BSomo
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
Thanks jib! Solved.
- BSomo
1 Answers
-1
votes
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.