H264 doesn't work in Firefox about jicofo

[bbaldino]

chrome doesn't seem to require the profile information in the offer, which is why we hadn't noticed this before when we were testing h264 with chrome. but we'll need to add a parameter extension in jicofo to add the profile information, like so:

addParameterExtension(h264, "profile-level-id",  "42e01f;level-asymmetry-allowed=1;packetization-mode=1"

chrome offers many different profiles, but firefox implements only 42e01f i think.

from chrome:

a=fmtp:100 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42001f
a=fmtp:102 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f
a=fmtp:107 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=4d0032
a=fmtp:109 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=640032

[rhwu]

This is affecting the newer version of Chrome as well.

H264 doesn't work when tested with Chrome 66.0.3359.181 on
https://meet.jit.si/demotest#config.preferH264=true&config.p2p.enabled=false&config.disableSimulcast=true

Looks like it's the below change that makes the different.
https://webrtc-review.googlesource.com/c/src/+/57820/4/media/base/codec.cc

[iclems]

@rhwu do you know what packetization mode Firefox expects?

[rhwu]

@iclems Not sure. Doesn't the suggested change work for you?

[bgrozev]

Re-open if still relevant