Closed Bug 1900194 Opened 5 months ago Closed 5 months ago

establishing webrtc session: firefox can't handle H264 baseline profile properly

Categories

(Core :: WebRTC, defect)

Product:
Core
Component:
WebRTC
Version:
Firefox 126
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1900114

People

(Reporter: robert.ayrapetyan, Unassigned)

Details

Steps to reproduce:

Media servier sends a following SDP offer to the Firefox browser:

0:00:02.997856279 110 0x7fe1d8002030 LOG webrtcsrc-signaller net/webrtc/src/signaller/imp.rs:172:gstrswebrtc::signaller::imp::Signaller::connect::{{closure}}::{{closure}}: Sending websocket message Peer(PeerMessage { session_id: "779eabe3-185c-4a8b-9c8d-a3533e4fe170", peer_message: Sdp(Offer { sdp: "v=0\r\no=- 1651929773769531913 0 IN IP4 0.0.0.0\r\ns=-\r\nt=0 0\r\na=ice-options:trickle\r\na=group:BUNDLE audio0 video1 application2\r\nm=audio 9 UDP/TLS/RTP/SAVPF 97\r\nc=IN IP4 0.0.0.0\r\na=setup:actpass\r\na=ice-ufrag:NHX7wOQIv3+QVhQwjquAWmhhJMxVPdg+\r\na=ice-pwd:QCIvj6q97YjR1ZpZXxuIh5sIjGXhRDNa\r\na=rtcp-mux\r\na=rtcp-rsize\r\na=sendonly\r\na=rtpmap:97 OPUS/48000/2\r\na=rtcp-fb:97 transport-cc\r\na=fmtp:97 sprop-stereo=1;sprop-maxcapturerate=48000\r\na=ssrc:2884313002 msid:user635498854@host-5d3b6a93 webrtctransceiver0\r\na=ssrc:2884313002 cname:user635498854@host-5d3b6a93\r\na=mid:audio0\r\na=fingerprint:sha-256 8C:F0:92:A2:D0:3D:89:3F:23:98:41:8A:9E:0B:20:B3:A7:59:B5:1C:A1:B3:D3:60:94:3B:75:D8:93:F3:0C:E2\r\na=rtcp-mux-only\r\nm=video 0 UDP/TLS/RTP/SAVPF 96 98 99 100 101\r\nc=IN IP4 0.0.0.0\r\na=setup:actpass\r\na=ice-ufrag:NHX7wOQIv3+QVhQwjquAWmhhJMxVPdg+\r\na=ice-pwd:QCIvj6q97YjR1ZpZXxuIh5sIjGXhRDNa\r\na=bundle-only\r\na=rtcp-mux\r\na=rtcp-rsize\r\na=sendonly\r\na=rtpmap:96 H264/90000\r\na=rtcp-fb:96 nack\r\na=rtcp-fb:96 nack pli\r\na=rtcp-fb:96 ccm fir\r\na=rtcp-fb:96 transport-cc\r\na=fmtp:96 packetization-mode=1;profile-level-id=42001f;level-asymmetry-allowed=1\r\na=rtpmap:98 red/90000\r\na=rtpmap:99 ulpfec/90000\r\na=rtpmap:100 rtx/90000\r\na=fmtp:100 apt=96\r\na=rtpmap:101 rtx/90000\r\na=fmtp:101 apt=98\r\na=ssrc-group:FID 2073974840 1890697951\r\na=ssrc:2073974840 msid:user635498854@host-5d3b6a93 webrtctransceiver1\r\na=ssrc:2073974840 cname:user635498854@host-5d3b6a93\r\na=ssrc:1890697951 msid:user635498854@host-5d3b6a93 webrtctransceiver1\r\na=ssrc:1890697951 cname:user635498854@host-5d3b6a93\r\na=mid:video1\r\na=fingerprint:sha-256 8C:F0:92:A2:D0:3D:89:3F:23:98:41:8A:9E:0B:20:B3:A7:59:B5:1C:A1:B3:D3:60:94:3B:75:D8:93:F3:0C:E2\r\na=rtcp-mux-only\r\nm=application 0 UDP/DTLS/SCTP webrtc-datachannel\r\nc=IN IP4 0.0.0.0\r\na=setup:actpass\r\na=ice-ufrag:NHX7wOQIv3+QVhQwjquAWmhhJMxVPdg+\r\na=ice-pwd:QCIvj6q97YjR1ZpZXxuIh5sIjGXhRDNa\r\na=bundle-only\r\na=mid:application2\r\na=sctp-port:5000\r\na=fingerprint:sha-256 8C:F0:92:A2:D0:3D:89:3F:23:98:41:8A:9E:0B:20:B3:A7:59:B5:1C:A1:B3:D3:60:94:3B:75:D8:93:F3:0C:E2\r\n" }) })

Actual results:

Firefox browser instance replies with:

0:00:03.159474297 110 0x7fe1d8002030 TRACE webrtcsrc-signaller net/webrtc/src/signaller/imp.rs:324:gstrswebrtc::signaller::imp::Signaller::handle_message:<GstWebRTCSignaller@0x55a917b7e190> Received message {"type": "peer", "sessionId": "779eabe3-185c-4a8b-9c8d-a3533e4fe170", "sdp": {"type": "answer", "sdp": "v=0\r\no=mozilla...THIS_IS_SDPARTA-99.0 8122336120804602734 0 IN IP4 0.0.0.0\r\ns=-\r\nt=0 0\r\na=sendrecv\r\na=fingerprint:sha-256 7C:1B:C8:3F:21:5A:0F:89:CA:4C:FD:55:27:57:98:9E:CF:34:E0:33:34:94:B6:D6:17:B5:E4:36:29:29:E1:1D\r\na=group:BUNDLE audio0 application2\r\na=ice-options:trickle\r\na=msid-semantic:WMS *\r\nm=audio 9 UDP/TLS/RTP/SAVPF 97\r\nc=IN IP4 0.0.0.0\r\na=recvonly\r\na=fmtp:97 maxplaybackrate=48000;stereo=1;useinbandfec=1\r\na=ice-pwd:388727abf16a0c4d1cd240abe35563a3\r\na=ice-ufrag:e1c83ff6\r\na=mid:audio0\r\na=rtcp-mux\r\na=rtpmap:97 opus/48000/2\r\na=setup:active\r\na=ssrc:2467474468 cname:{24129c2a-a2dd-4336-913d-6e7232f89910}\r\nm=video 0 UDP/TLS/RTP/SAVPF 120\r\nc=IN IP4 0.0.0.0\r\na=inactive\r\na=mid:video1\r\na=rtpmap:120 VP8/90000\r\nm=application 9 UDP/DTLS/SCTP webrtc-datachannel\r\nc=IN IP4 0.0.0.0\r\na=sendrecv\r\na=ice-pwd:388727abf16a0c4d1cd240abe35563a3\r\na=ice-ufrag:e1c83ff6\r\na=mid:application2\r\na=setup:active\r\na=sctp-port:5000\r\na=max-message-size:1073741823\r\n"}}

Expected results:

Firefox should accept H264 offer and reply with H264 active response.

The Bugbug bot thinks this bug should belong to the 'Core::WebRTC' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → WebRTC
Product: Firefox → Core

Changing profile from H264 "baseline" to "main" on the server side resolved the issue.

OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Summary: establishing webrtc session: firefox replies "V8 inactive" for h264 sdp offer → establishing webrtc session: firefox can't handle H264 baseline profile properly

(reformatted with newlines) Steps to reproduce:

Media servier sends a following SDP offer to the Firefox browser:

0:00:02.997856279 110 0x7fe1d8002030 LOG webrtcsrc-signaller net/webrtc/src/signaller/imp.rs:172:gstrswebrtc::signaller::imp::Signaller::connect::{{closure}}::{{closure}}: Sending websocket message Peer(PeerMessage { session_id: "779eabe3-185c-4a8b-9c8d-a3533e4fe170", peer_message: Sdp(Offer { sdp: "

v=0
o=- 1651929773769531913 0 IN IP4 0.0.0.0
s=-
t=0 0
a=ice-options:trickle
a=group:BUNDLE audio0 video1 application2
m=audio 9 UDP/TLS/RTP/SAVPF 97
c=IN IP4 0.0.0.0
a=setup:actpass
a=ice-ufrag:NHX7wOQIv3+QVhQwjquAWmhhJMxVPdg+
a=ice-pwd:QCIvj6q97YjR1ZpZXxuIh5sIjGXhRDNa
a=rtcp-mux
a=rtcp-rsize
a=sendonly
a=rtpmap:97 OPUS/48000/2
a=rtcp-fb:97 transport-cc
a=fmtp:97 sprop-stereo=1;sprop-maxcapturerate=48000
a=ssrc:2884313002 msid:user635498854@host-5d3b6a93 webrtctransceiver0
a=ssrc:2884313002 cname:user635498854@host-5d3b6a93
a=mid:audio0
a=fingerprint:sha-256 8C:F0:92:A2:D0:3D:89:3F:23:98:41:8A:9E:0B:20:B3:A7:59:B5:1C:A1:B3:D3:60:94:3B:75:D8:93:F3:0C:E2
a=rtcp-mux-only
m=video 0 UDP/TLS/RTP/SAVPF 96 98 99 100 101
c=IN IP4 0.0.0.0
a=setup:actpass
a=ice-ufrag:NHX7wOQIv3+QVhQwjquAWmhhJMxVPdg+
a=ice-pwd:QCIvj6q97YjR1ZpZXxuIh5sIjGXhRDNa
a=bundle-only
a=rtcp-mux
a=rtcp-rsize
a=sendonly
a=rtpmap:96 H264/90000
a=rtcp-fb:96 nack
a=rtcp-fb:96 nack pli
a=rtcp-fb:96 ccm fir
a=rtcp-fb:96 transport-cc
a=fmtp:96 packetization-mode=1;profile-level-id=42001f;level-asymmetry-allowed=1
a=rtpmap:98 red/90000
a=rtpmap:99 ulpfec/90000
a=rtpmap:100 rtx/90000
a=fmtp:100 apt=96
a=rtpmap:101 rtx/90000
a=fmtp:101 apt=98
a=ssrc-group:FID 2073974840 1890697951
a=ssrc:2073974840 msid:user635498854@host-5d3b6a93 webrtctransceiver1
a=ssrc:2073974840 cname:user635498854@host-5d3b6a93
a=ssrc:1890697951 msid:user635498854@host-5d3b6a93 webrtctransceiver1
a=ssrc:1890697951 cname:user635498854@host-5d3b6a93
a=mid:video1
a=fingerprint:sha-256 8C:F0:92:A2:D0:3D:89:3F:23:98:41:8A:9E:0B:20:B3:A7:59:B5:1C:A1:B3:D3:60:94:3B:75:D8:93:F3:0C:E2
a=rtcp-mux-only
m=application 0 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 0.0.0.0
a=setup:actpass
a=ice-ufrag:NHX7wOQIv3+QVhQwjquAWmhhJMxVPdg+
a=ice-pwd:QCIvj6q97YjR1ZpZXxuIh5sIjGXhRDNa
a=bundle-only
a=mid:application2
a=sctp-port:5000
a=fingerprint:sha-256 8C:F0:92:A2:D0:3D:89:3F:23:98:41:8A:9E:0B:20:B3:A7:59:B5:1C:A1:B3:D3:60:94:3B:75:D8:93:F3:0C:E2

" }) })

Actual results:

Firefox browser instance replies with:

0:00:03.159474297 110 0x7fe1d8002030 TRACE webrtcsrc-signaller net/webrtc/src/signaller/imp.rs:324:gstrswebrtc::signaller::imp::Signaller::handle_message:<GstWebRTCSignaller@0x55a917b7e190> Received message {"type": "peer", "sessionId": "779eabe3-185c-4a8b-9c8d-a3533e4fe170", "sdp": {"type": "answer", "sdp": "

v=0
o=mozilla...THIS_IS_SDPARTA-99.0 8122336120804602734 0 IN IP4 0.0.0.0
s=-
t=0 0
a=sendrecv
a=fingerprint:sha-256 7C:1B:C8:3F:21:5A:0F:89:CA:4C:FD:55:27:57:98:9E:CF:34:E0:33:34:94:B6:D6:17:B5:E4:36:29:29:E1:1D
a=group:BUNDLE audio0 application2
a=ice-options:trickle
a=msid-semantic:WMS *
m=audio 9 UDP/TLS/RTP/SAVPF 97
c=IN IP4 0.0.0.0
a=recvonly
a=fmtp:97 maxplaybackrate=48000;stereo=1;useinbandfec=1
a=ice-pwd:388727abf16a0c4d1cd240abe35563a3
a=ice-ufrag:e1c83ff6
a=mid:audio0
a=rtcp-mux
a=rtpmap:97 opus/48000/2
a=setup:active
a=ssrc:2467474468 cname:{24129c2a-a2dd-4336-913d-6e7232f89910}
m=video 0 UDP/TLS/RTP/SAVPF 120
c=IN IP4 0.0.0.0
a=inactive
a=mid:video1
a=rtpmap:120 VP8/90000
m=application 9 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 0.0.0.0
a=sendrecv
a=ice-pwd:388727abf16a0c4d1cd240abe35563a3
a=ice-ufrag:e1c83ff6
a=mid:application2
a=setup:active
a=sctp-port:5000
a=max-message-size:1073741823

"}}

Expected results:

Firefox should accept H264 offer and reply with H264 active response.

Flags: needinfo?(docfaraday)

This is because we do not currently have H264 baseline in our list of codecs. Dan is almost done adding that over in bug 1900114.

Status: UNCONFIRMED → RESOLVED
Closed: 5 months ago
Duplicate of bug: 1900114
Flags: needinfo?(docfaraday)
Resolution: --- → DUPLICATE

Byron, somehow constraint-baseline profile works fine...

Right, we support constrained baseline, but not baseline, at least until bug 1900114 lands.

You need to log in before you can comment on or make changes to this bug.