Wire up transport sequence number / send time callbacks to webrtc via libjingle.

talk/media/base/constants.cc

Index: talk/media/base/constants.cc
diff --git a/talk/media/base/constants.cc b/talk/media/base/constants.cc
index 0d0a33c18aad2bcc58b6c3a2207f0097a6c9da44..dcfa5869fb9ad77ff6d8c9520c70766d6b7544fe 100644
--- a/talk/media/base/constants.cc
+++ b/talk/media/base/constants.cc
@@ -90,6 +90,7 @@ const int kPreferredUseInbandFec = 0;
 const char kRtcpFbParamNack[] = "nack";
 const char kRtcpFbNackParamPli[] = "pli";
 const char kRtcpFbParamRemb[] = "goog-remb";
+const char kRtcpFbParamTransport[] = "goog-transport-fb";

[pthatcher1, 2015/09/25 23:24:57]

Are we avoiding "goog" prefixes?  

And can we come up with a more descriptive name?  Perhaps "transport-seq-num"?

[stefan-webrtc, 2015/10/02 13:29:12]

This is actually an rtcp message. Renaming it transport-cc-fb.

 
 const char kRtcpFbParamCcm[] = "ccm";
 const char kRtcpFbCcmParamFir[] = "fir";
@@ -124,6 +125,10 @@ const char kRtpVideoRotationHeaderExtension[] = "urn:3gpp:video-orientation";
 const char kRtpVideoRotation6BitsHeaderExtensionForTesting[] =
     "urn:3gpp:video-orientation:6";
 
+const int kRtpTransportSequenceNumberHeaderExtensionDefaultId = 5;
+const char kRtpTransportSequenceNumberHeaderExtension[] =
+    "http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions";
+
 const int kNumDefaultUnsignalledVideoRecvStreams = 0;
 
 const char kVp8CodecName[] = "VP8";