# RR for video has sender source 1

**URL:** <https://mediasoup.discourse.group/t/rr-for-video-has-sender-source-1/5091>\
**Category:** mediasoup libraries\
**Created:** [March 26, 2023, 3:01pm UTC](https://mediasoup.discourse.group/t/rr-for-video-has-sender-source-1/5091 "2023-03-26T15:01:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manish](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@Manish](https://mediasoup.discourse.group/u/Manish)\
**Post date:** [March 26, 2023, 3:01pm UTC](https://mediasoup.discourse.group/t/rr-for-video-has-sender-source-1/5091/1 "2023-03-26T15:01:08Z")

</div>

I have captured the RR sent by the browser to the SFU and seen that for the video consumer browser sends the RR with the sender source as 1 but for the audio consumer it contains a valid sender source as same as the ssrc of the consumer. Is this a bug?

Image ref - 1st one is for video consumer and 2nd one is for audio consumer.

 ![Video consumer RR](https://global.discourse-cdn.com/free1/uploads/mediasoup/original/2X/4/49b3cfcbb36c43f04a642371c699f84796a919fb.png)  
 ![audio consumer RR](https://global.discourse-cdn.com/free1/uploads/mediasoup/original/2X/e/ed6ed861ef79d25ac91db2e0780e7042a8a5b9f4.png)

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [March 26, 2023, 3:42pm UTC](https://mediasoup.discourse.group/t/rr-for-video-has-sender-source-1/5091/2 "2023-03-26T15:42:09Z")

</div>

No, it’s not a bug. Check the RTCP Receiver Report spec and you’ll see that this is ok.

---

<div class="post-metadata">

**Author:** ![Manish](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@Manish](https://mediasoup.discourse.group/u/Manish)\
**Post date:** [March 27, 2023, 3:39am UTC](https://mediasoup.discourse.group/t/rr-for-video-has-sender-source-1/5091/3 "2023-03-27T03:39:04Z")

</div>

Does this mean mediasoup doesn’t handle video consumer RR packets?

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [March 27, 2023, 5:37am UTC](https://mediasoup.discourse.group/t/rr-for-video-has-sender-source-1/5091/4 "2023-03-27T05:37:25Z")

</div>

mediasoup handles all RTCP including RR.

---

<div class="post-metadata">

**Author:** ![Manish](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@Manish](https://mediasoup.discourse.group/u/Manish)\
**Post date:** [March 27, 2023, 6:06am UTC](https://mediasoup.discourse.group/t/rr-for-video-has-sender-source-1/5091/5 "2023-03-27T06:06:23Z")

</div>

Just a small question since the sender ssrc is 1 how does mediasoup map that RTCP RR report to consumer?

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [March 27, 2023, 7:39am UTC](https://mediasoup.discourse.group/t/rr-for-video-has-sender-source-1/5091/6 "2023-03-27T07:39:52Z")

</div>

Because the field to check is not that but another present in the RR. Please check the RTP spec.

---

<div class="post-metadata">

**Author:** ![Manish](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@Manish](https://mediasoup.discourse.group/u/Manish)\
**Post date:** [March 27, 2023, 10:38am UTC](https://mediasoup.discourse.group/t/rr-for-video-has-sender-source-1/5091/7 "2023-03-27T10:38:27Z")

</div>

Thanks, @ibc.