Error Detail Type: Failed to set remote offer sdp: Failed to set remote video description send param

I have this error when trying to set the remote description. I’m using version 2.3.1 WebRTC plugin. Is there anyone that knows what’s going on?

Error Detail Type: Failed to set remote offer sdp: Failed to set remote video description send parameters for m-section with mid='1

the sdp is this:

v=0
o=- 7299763484283908201 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE 0 1 2
a=msid-semantic: WMS
m=audio 9 UDP/TLS/RTP/SAVPF 111 110
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:x7SG
a=ice-pwd:6nlfUcWoXc0ojF+4tBj6V7WO
a=ice-options:trickle
a=fingerprint:sha-256  HIDDEN
a=setup:actpass
a=mid:0
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid
a=extmap:5 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id
a=extmap:6 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id
a=recvonly
a=rtcp-mux
a=rtpmap:111 opus/48000/2
a=rtcp-fb:111 transport-cc
a=fmtp:111 minptime=10;useinbandfec=1
a=rtpmap:110 telephone-event/48000
m=video 9 UDP/TLS/RTP/SAVPF 127 126 125 102 103 104 105 98 99 100
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:x7SG
a=ice-pwd:6nlfUcWoXc0ojF+4tBj6V7WO
a=ice-options:trickle
a=fingerprint:sha-256 HIDDEN
a=setup:actpass
a=mid:1
a=extmap:14 urn:ietf:params:rtp-hdrext:toffset
a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:13 urn:3gpp:video-orientation
a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
a=extmap:12 http://www.webrtc.org/experiments/rtp-hdrext/playout-delay
a=extmap:11 http://www.webrtc.org/experiments/rtp-hdrext/video-content-type
a=extmap:7 http://www.webrtc.org/experiments/rtp-hdrext/video-timing
a=extmap:8 http://www.webrtc.org/experiments/rtp-hdrext/color-space
a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid
a=extmap:5 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id
a=extmap:6 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id
a=recvonly
a=rtcp-mux
a=rtcp-rsize
a=rtpmap:127 VP8/90000
a=rtcp-fb:127 goog-remb
a=rtcp-fb:127 transport-cc
a=rtcp-fb:127 ccm fir
a=rtcp-fb:127 nack
a=rtcp-fb:127 nack pli
a=rtpmap:126 VP9/90000
a=rtcp-fb:126 goog-remb
a=rtcp-fb:126 transport-cc
a=rtcp-fb:126 ccm fir
a=rtcp-fb:126 nack
a=rtcp-fb:126 nack pli
a=fmtp:126 profile-id=0
a=rtpmap:125 VP9/90000
a=rtcp-fb:125 goog-remb
a=rtcp-fb:125 transport-cc
a=rtcp-fb:125 ccm fir
a=rtcp-fb:125 nack
a=rtcp-fb:125 nack pli
a=fmtp:125 profile-id=2
a=rtpmap:102 VP9/90000
a=rtcp-fb:102 goog-remb
a=rtcp-fb:102 transport-cc
a=rtcp-fb:102 ccm fir
a=rtcp-fb:102 nack
a=rtcp-fb:102 nack pli
a=fmtp:102 profile-id=1
a=rtpmap:103 rtx/90000
a=fmtp:103 apt=102
a=rtpmap:104 AV1X/90000
a=rtcp-fb:104 goog-remb
a=rtcp-fb:104 transport-cc
a=rtcp-fb:104 ccm fir
a=rtcp-fb:104 nack
a=rtcp-fb:104 nack pli
a=rtpmap:105 rtx/90000
a=fmtp:105 apt=104
a=rtpmap:98 red/90000
a=rtpmap:99 rtx/90000
a=fmtp:99 apt=98
a=rtpmap:100 ulpfec/90000
m=application 9 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 0.0.0.0
a=ice-ufrag:x7SG
a=ice-pwd:6nlfUcWoXc0ojF+4tBj6V7WO
a=ice-options:trickle
a=fingerprint:sha-256 HIDDEN
a=setup:actpass
a=mid:2
a=sctp-port:5000
a=max-message-size:262144

Can I have a minimum project to reproduce the issue?
Thanks

Let me try. I’m using a Signaler Server to pass the Offer from peer to peer, instead of “GetOtherPc” function in the examples. So I’m reconstructing the RTCSessionDescription object in the remote side(callee). The sdp string is identical to the one that was generated to the local peer (caller) and the type is properly set in the initial data. But trying to set this new created object with the SetRemoteDescription produces this error. This only happens when RECONSTRUCTING RTCSessionDescription from type and sdp string. It doesn’t happen in the examples where the RTCSessionDescription object is passed by ref.

This issue could be related to yours.
Unity Render Streaming Introduction & FAQ page-12#post-6760897