Failed to set remote answer sdp: Called in wrong state: STATE_INPROGRESS
See original GitHub issueWhen Trickle ICE is enabled, I get the following error when trying to establish a peer connection between two Chrome browsers on the same machine:
Failed to set remote answer sdp: Called in wrong state: STATE_INPROGRESS
Disabling Trickle ICE, everything works smoothly.
The code I’m testing with is in a gist: https://gist.github.com/adammw/d9bf021c395835427aa0
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Failed to set remote answer sdp: Called in wrong state
Here is my code: var peerConnections = {}; var mainStream; var currentId; navigator.getUserMedia( { audio: true, video ...
Read more >Failed to set remote answer sdp: Called in wrong state ...
If I initiate sessions with a stream of both audio and video tracks I randomly get errors either setting local or remote answer...
Read more >Failed to set remote answer sdp: Called in wrong state ...
Coding example for the question WebRTC - Failed to set remote answer sdp: Called in wrong state: STATE_INPROGRESS-webrtc.
Read more >3410 - Failed to set remote offer sdp: Called in wrong state
Hi Braveyao, Thanks for the response, This was the offer SDP problem, instead of answer SDP, offer SDP is sent.
Read more >SDP answer received, setting remote description Failed to set ...
SDP answer received, setting remote description Failed to set remote answer sdp: Called in wrong state: STATE_INPROGRESS. 796 views.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Btw, you shouldn’t add a new set of event listeners in
socket.on('receivePeerSignal', function(data) {
because that will get called multiple times with each bit of signaling data and you’ll end up handling the 'connec’t and ‘data’ events multiple times.Thanks that actually helped save me on another project I was working on 😃