Move RtcEventLog object from inside VoiceEngine to Call.

webrtc/api/peerconnectionfactory.cc

Index: webrtc/api/peerconnectionfactory.cc
diff --git a/webrtc/api/peerconnectionfactory.cc b/webrtc/api/peerconnectionfactory.cc
index c05cd852f605faada5dbd47e68e7b2ec8afd94e8..9344f784c621a8b15272ae2f980eff46190d5b8c 100644
--- a/webrtc/api/peerconnectionfactory.cc
+++ b/webrtc/api/peerconnectionfactory.cc
@@ -219,16 +219,6 @@ void PeerConnectionFactory::StopAecDump() {
   channel_manager_->StopAecDump();
 }
 
-bool PeerConnectionFactory::StartRtcEventLog(rtc::PlatformFile file) {

[terelius, 2016/03/10 10:42:32]

I'm sorry, but I don't see why it is safe to effectively disable these calls
immediately. Won't this mean that the button on the webrtc-internals page will
stop working until Chrome has been updated? If so, I think it would be better to
keep them for now and remove them in the clean-up CL you are planning anyway.

[ivoc, 2016/03/10 13:15:36]

Note that the functions still exist on PeerConnectionFactoryInterface, they will
just stop working until Chrome is updated. I was planning to make a Chrome CL
and land it soon after landing this one (wait until both are approved before
landing). I couldn't think of a way to keep both these functions working as well
as the new ones in PeerConnectionInterface. Let me know if you have a better
idea for how to handle this.

-  RTC_DCHECK(signaling_thread_->IsCurrent());
-  return channel_manager_->StartRtcEventLog(file);
-}
-
-void PeerConnectionFactory::StopRtcEventLog() {
-  RTC_DCHECK(signaling_thread_->IsCurrent());
-  channel_manager_->StopRtcEventLog();
-}
-
 rtc::scoped_refptr<PeerConnectionInterface>
 PeerConnectionFactory::CreatePeerConnection(
     const PeerConnectionInterface::RTCConfiguration& configuration,