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

talk/app/webrtc/mediacontroller.h

Index: talk/app/webrtc/mediacontroller.h
diff --git a/talk/app/webrtc/mediacontroller.h b/talk/app/webrtc/mediacontroller.h
index 68798515d00984c586a88fbf8346f75ca96f309b..8fa72c6e18f9850641a86212365af84ca9e470ac 100644
--- a/talk/app/webrtc/mediacontroller.h
+++ b/talk/app/webrtc/mediacontroller.h
@@ -29,6 +29,7 @@
 #define TALK_APP_WEBRTC_MEDIACONTROLLER_H_
 
 #include "webrtc/base/thread.h"
+#include "webrtc/common_types.h"
 
 namespace webrtc {
 class Call;
@@ -43,6 +44,8 @@ class MediaControllerInterface {
 
   virtual ~MediaControllerInterface() {}
   virtual webrtc::Call* call_w() = 0;
+
+  virtual void OnPacketSent(const webrtc::SentPacket& sent_packet) = 0;

[pthatcher1, 2015/10/05 18:30:13]

Are we sure that packet_ids will not collide when we bundle audio and video over
the same transport?  If they do, this will cause problems.  If they don't, then
we're fine.

[pthatcher1, 2015/10/05 18:30:13]

Why would a caller call media_controller_->OnPacketSent(sp) instead of
media_controller_->call_w()->OnPacketSent(sp)?

[stefan-webrtc, 2015/10/06 13:00:19]

That is the point with this packet id. It's a sequence number which increases by
1 for each packet sent over the same port. I'm currently making the assumption
that all packets sent by a PC are sent on the same underlying port, which is the
same assumption we have been doing before for BWE.

[pthatcher1, 2015/10/06 20:23:55]

Each port only has one PC, yes.  

 };
 }  // namespace webrtc