Add SetReportBlocks to rtcp Sender/Receive Report classes.

webrtc/modules/rtp_rtcp/source/rtcp_packet/receiver_report.h

Index: webrtc/modules/rtp_rtcp/source/rtcp_packet/receiver_report.h
diff --git a/webrtc/modules/rtp_rtcp/source/rtcp_packet/receiver_report.h b/webrtc/modules/rtp_rtcp/source/rtcp_packet/receiver_report.h
index 85ab8ebd347acec775fbcfd2b194572b3f9689d0..1b08f6404cea1d31c80d505c89eecdf1ce733985 100644
--- a/webrtc/modules/rtp_rtcp/source/rtcp_packet/receiver_report.h
+++ b/webrtc/modules/rtp_rtcp/source/rtcp_packet/receiver_report.h
@@ -24,6 +24,8 @@ class CommonHeader;
 class ReceiverReport : public RtcpPacket {
  public:
   static constexpr uint8_t kPacketType = 201;
+  static constexpr size_t kMaxNumberOfReportBlocks = 0x1f;

[eladalon, 2017/07/25 13:26:09]

(Not actionable.)
Does this correspond to a field of 5 bits? I wonder why the limit isn't 32, btw.
Is it every possible to have 0 blocks? If not, they could have made 0 mean 1
report, 1 mean 2 report, etc., up to 31 meaning 32 reports.

[danilchap, 2017/07/25 13:39:00]

yes, there are 5 bits to store number of report blocks.
0 report blocks is valid and common (specially for sender reports)
See rfc3550, section 6.4.1/6.4.2

+
   ReceiverReport();
   ~ReceiverReport() override;
 
@@ -32,6 +34,7 @@ class ReceiverReport : public RtcpPacket {
 
   void SetSenderSsrc(uint32_t ssrc) { sender_ssrc_ = ssrc; }
   bool AddReportBlock(const ReportBlock& block);
+  bool SetReportBlocks(std::vector<ReportBlock> blocks);
 
   uint32_t sender_ssrc() const { return sender_ssrc_; }
   const std::vector<ReportBlock>& report_blocks() const {
@@ -47,7 +50,6 @@ class ReceiverReport : public RtcpPacket {
 
  private:
   static const size_t kRrBaseLength = 4;
-  static const size_t kMaxNumberOfReportBlocks = 0x1F;
 
   uint32_t sender_ssrc_;
   std::vector<ReportBlock> report_blocks_;