Wire up RTP keep-alive in ortc api.

webrtc/call/call.h

Index: webrtc/call/call.h
diff --git a/webrtc/call/call.h b/webrtc/call/call.h
index f99ba851ab420daeb5c12f03e1577f1701c4cbb3..d4149f1b52b2b2fc127640925e50ba1487cb80af 100644
--- a/webrtc/call/call.h
+++ b/webrtc/call/call.h
@@ -205,6 +205,10 @@ class Call {
 
   virtual void OnSentPacket(const rtc::SentPacket& sent_packet) = 0;
 
+  // Try to update the RTP keep-alive part of the call config. This is allowed
+  // only before creating any send streams. Returns true on success.
+  virtual bool SetRtpKeepAliveConfig(const RtpKeepAliveConfig& config) = 0;

[stefan-webrtc, 2017/08/08 08:13:06]

Is there a reason why we have to set this after we create Call? Seems like a
step in the wrong direction.

[sprang_webrtc, 2017/08/08 08:53:30]

I know, it was my intention to have this at construction time, but due to where
the Call instance lives (in the RtpTransportControllerAdapter), it get's
complicated as we want the parameters to be set on the RtpTransport interface of
the ORTC API...

+
   virtual ~Call() {}
 };