H.264 packetization mode 0 (try 2)

webrtc/modules/video_coding/codec_database.cc

Index: webrtc/modules/video_coding/codec_database.cc
diff --git a/webrtc/modules/video_coding/codec_database.cc b/webrtc/modules/video_coding/codec_database.cc
index 48ca1fbe25b2b672328eb5e8a6f0e3beb824904e..bdc1fd1e737f7b6b83aa6f7a7886bead2f10326c 100644
--- a/webrtc/modules/video_coding/codec_database.cc
+++ b/webrtc/modules/video_coding/codec_database.cc
@@ -65,6 +65,7 @@ VideoCodecH264 VideoEncoder::GetDefaultH264Settings() {
   h264_settings.profile = kProfileBase;
   h264_settings.frameDroppingOn = true;
   h264_settings.keyFrameInterval = 3000;
+  h264_settings.packetization_mode = kH264PacketizationMode1;

[hbos, 2016/10/31 10:32:26]

Similar question as earlier: Should the default be 0 or 1? If missing in the
SDP, it should be 0?

[hta-webrtc, 2016/10/31 15:03:04]

The whole stack expects 1 at this time, and info from others (Cisco) indicates
that the only people using mode 0 are some "special" (=old) devices, mostly
telephone gateways. So keeping it at 1 is a lower risk.

[hbos, 2016/10/31 16:27:15]

Acknowledged.

   h264_settings.spsData = nullptr;
   h264_settings.spsLen = 0;
   h264_settings.ppsData = nullptr;