Failed to set remote video description send parameters for m-section with mid='0'.

636 views
Skip to first unread message

Kyle Dias

unread,
Aug 7, 2021, 7:57:58 AM8/7/21
to discuss-webrtc
Hi,

I am creating a client using the WebRTC-Java API. I have not yet created any media stream tracks or have any renders setup as I only am trying to get the signalling working. However when I try to set the remote sdp offer I get this error:

Failed to set remote video description send parameters for m-section with mid='0'.

Anyone know what this error means and how to fix it? I am able to connect using the JS API and using chrome but not when using an android application using the Java API. The full remote offer sdp is below. 

Any help would be greatly appreciated. Thanks.

"v=0
 o=- 3045291557152081733 2 
IN IP4 127.0.0.1 
s=- t=0 0 
a=group:BUNDLE 0 1 2 
a=msid-semantic: WMS audio display_0 
m=video 9 UDP/TLS/RTP/SAVPF 96 97 98 99 100 
c=IN IP4 0.0.0.0 
a=rtcp:9 IN IP4 0.0.0.0 
a=ice-ufrag:zY5b 
a=ice-pwd:FjrC6bk446HZC4tuLzUxFxYT 
a=ice-options:trickle 
a=fingerprint:sha-256 45:15:FB:CB:95:5C:78:8F:07:69:76:B3:7B:D5:85:7A:A2:A5:82:C1:6E:3F:1C:4B:21:93:73:45:50:BA:AC:29 
a=setup:actpass 
a=mid:0 
a=extmap:1 urn:ietf:params:rtp-hdrext:toffset a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time a=extmap:3 urn:3gpp:video-orientation a=extmap:4 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01 
a=extmap:10 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id a=extmap:11 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id 
a=sendrecv a=msid:display_0 display_0 
a=rtcp-mux a=rtcp-rsize a=rtpmap:96 VP8/90000 
a=rtcp-fb:96 goog-remb a=rtcp-fb:96 transport-cc 
a=rtcp-fb:96 ccm fir 
a=rtcp-fb:96 nack 
a=rtcp-fb:96 nack pli 
a=rtpmap:97 rtx/90000 
a=fmtp:97 apt=96 
a=rtpmap:98 red/90000 
a=rtpmap:99 rtx/90000 
a=fmtp:99 apt=98 
a=rtpmap:100 ulpfec/90000 
a=ssrc-group:FID 746653947 2239989715 
a=ssrc:746653947 cname:35R1BxmMMWAnEJkV 
a=ssrc:746653947 msid:display_0 display_0 
a=ssrc:746653947 mslabel:display_0 
a=ssrc:746653947 label:display_0 
a=ssrc:2239989715 cname:35R1BxmMMWAnEJkV 
a=ssrc:2239989715 msid:display_0 display_0 
a=ssrc:2239989715 mslabel:display_0 
a=ssrc:2239989715 label:display_0 

Thanks,
Kyle

Kyle Dias

unread,
Aug 7, 2021, 8:56:16 PM8/7/21
to discuss-webrtc

After getting the WebRTC log. The failure is due to:

E/webrtc_video_engine.cc: (line 745): No video codecs supported.
E/peer_connection.cc: (line 6009): Failed to set remote video description send parameters for m-section with mid='0'. (INVALID_PARAMETER)
    (line 3097): Failed to set remote offer sdp: Failed to set remote video description send parameters for m-section with mid='0'.

However it also shows that I am sending VP8 codec:
SetSendParameters: {codecs: [VideoCodec[96:VP8], VideoCodec[97:rtx], VideoCodec[98:red], VideoCodec[99:rtx], VideoCodec[100:ulpfec]],

Going over the Android doc shows that the latest SDKs still support VP8 and on all devices. Do I need to manually change the received remote sdp before setting it?

Any idea why this error is thrown?

Thanks,
Kyle
Reply all
Reply to author
Forward
0 new messages