Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote offer sdp: Failed to add remote stream ssrc: 3735143948 to {mid: 5, media_type: video}

[balb...@gmail.com]

error log in chrome.log:

[15792:16576:1220/123421.937:ERROR:webrtc_video_engine.cc(2823)] Receive stream with SSRC '2606321315' already exists.
[15792:17284:1220/123421.938:ERROR:sdp_offer_answer.cc(4895)] Failed to add remote stream ssrc: 2606321315 to {mid: 7, media_type: video} (INVALID_PARAMETER)
[15792:17284:1220/123421.938:ERROR:sdp_offer_answer.cc(946)] Failed to set remote offer sdp: Failed to add remote stream ssrc: 2606321315 to {mid: 7, media_type: video}

all sdp in attachments

[Harald Alvestrand]

This seems to belong in a Chrome bug report.

A Chrome bug report should also include which Chrome version you have, and the offer. Preferably a script that reproduces the issue, but that's often infeasible; a description of how the issue happened can often replace that.

--
This list falls under the WebRTC Code of Conduct - https://webrtc.org/support/code-of-conduct.
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/db7daa77-4d81-4348-ab8a-6b1aba6434a2n%40googlegroups.com.

[Philipp Hancke]

Well, the sdp log does not show the ssrc from the error so it is a bit hard to debug  this further.

Since the SDP says "Janus" have you asked in the Janus discourse?

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAOqqYVHoGqe4uezpGQJRr3tdymNghB2p50o%2B%2BOojEE38uG7Jug%40mail.gmail.com.

[balb...@gmail.com]

sorry, the ssrc in title didn't match the sdp, but  ssrc in the chome.log  match the sdp.

i can't edit the title 

the error report from   code of chome webrtc, so  i first report the bug here

i report this bug to  Janus discourse later

[Philipp Hancke]

Looking at the code you will need to also look for prior log messages about AddRecvStream originating from

https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/media/engine/webrtc_video_engine.cc;l=2846;drc=8e78783dc1f7007bad46d657c9f332614e240fd8;bpv=1;bpt=1

If the server sends media before waiting for an answer receiving a packet on a certain mid/ssrc might create a receive stream which leads to the collision.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/c118168b-e921-4c86-a88a-a8e78b239e3an%40googlegroups.com.

[balb...@gmail.com]

when the issue appears, i find a stream which ssrc = 14795 and rtxSsrc = real ssrc in webrtc-internal