GNOME Bugzilla – Bug 795939
webrtcbin: Lack of mandatory fields in offer SDP in case of h.264 stream
Last modified: 2018-05-09 13:18:52 UTC
When webrtcbin forms sdp for an offer it doesn't add such params as packetization-mode, profile-level-id, etc. It's seems like since Google Chrome updated to version 66 at least packetization-mode parameter is required and Chrome fails to create an answer when this param not presented in SDP for remote description. Modifying offer's sdp in js by adding packetization-mode=1 makes video working in Chrome 66.
I can confirm this. Perhaps related to https://bugzilla.gnome.org/show_bug.cgi?id=795404 How are you working around this (other than modifying in js)?
Yes, the point is when I've tried to figure it out I found that webrtcbin uses rtp payloader's src pad caps during the forming of offer, it happens in NULL => READY state change which means webrtcbin uses default rtp payloader caps before the stream was parsed and caps were clarified.
(In reply to Ilya Smelykh from comment #2) > Yes, the point is when I've tried to figure it out I found that webrtcbin > uses rtp payloader's src pad caps during the forming of offer, it happens in > NULL => READY state change which means webrtcbin uses default rtp payloader > caps before the stream was parsed and caps were clarified. What if you link the bin after the payloader get its caps? How would you do that?
This should be fixed as a side effect of bug 795044.
(In reply to Matthew Waters (ystreet00) from comment #4) > This should be fixed as a side effect of bug 795044. Yep, this patch fixes the problem.
*** This bug has been marked as a duplicate of bug 795044 ***