commit 3fc40106b0c32d06ac3d5ebc59a78565263c6ec6
author Lambros Lambrou <lambroslambrou@chromium.org> Wed Jan 16 01:56:56 2019
committer Commit Bot <commit-bot@chromium.org> Wed Jan 16 01:56:56 2019
tree 99fb6e15c4d523acd63125d2db0e37eb94f0a950
parent 117922c7e66e9bcfd72bad3f25bba42ce3793329

Set bitrate caps using newer APIs

This removes the x-google-[min/max]-bitrate SDP parameters used to set
the bandwidth caps for the connection. Instead, the global caps are
set using PeerConnection::SetBitrate(), and the VideoSender caps are
set to the same values using RtpSender::SetParameters(), which was
already being used to set the max-bitrate cap for relay connections.
It appears that both global and per-sender caps are needed to
properly configure the b/w estimator and ALR probers, otherwise the
bitrate is severely constrained by WebRTC defaults (~600kbps).

This CL unblocks the UnifiedPlan migration, and ensures we are using
consistent APIs to set the bitrate caps for both direct and relayed
connections.

Bug: 903012, 833538
Change-Id: Iefaddf877071f0fc3a010cf02a2b1fd2a92ad00c
Reviewed-on: https://chromium-review.googlesource.com/c/1409710
Reviewed-by: Joe Downing <joedow@chromium.org>
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#623014}