# consuming media from pipeToRouter call

**URL:** <https://mediasoup.discourse.group/t/consuming-media-from-pipetorouter-call/6549>\
**Category:** mediasoup libraries\
**Created:** [March 11, 2025, 3:01pm UTC](https://mediasoup.discourse.group/t/consuming-media-from-pipetorouter-call/6549 "2025-03-11T15:01:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pksinghus](https://avatars.discourse-cdn.com/v4/letter/p/9fc348/32.png) [@pksinghus](https://mediasoup.discourse.group/u/pksinghus)\
**Post date:** [March 11, 2025, 3:01pm UTC](https://mediasoup.discourse.group/t/consuming-media-from-pipetorouter-call/6549/1 "2025-03-11T15:01:05Z")

</div>

After a peer has been piped in to a router by using [pipeToRouter](https://mediasoup.org/documentation/v3/mediasoup/api/#router-pipeToRouter) (by piping in all its producers), how do I consume its media in the demo application? The demo works on Peer objects. After piping in a producer I didn’t see any notifications (piping hasn’t worked fully, I am still experimenting).

Should I create a Peer object and notify others using protoo that there is a new Peer? Should I introduce a new notification that there is a pipedPeer with these producers? Should I just send a newConsumer notification on protoo with the piped in producer’s info?

---

<div class="post-metadata">

**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\
**Post date:** [March 11, 2025, 8:45pm UTC](https://mediasoup.discourse.group/t/consuming-media-from-pipetorouter-call/6549/2 "2025-03-11T20:45:27Z")

</div>

Your signaling logic should be able to alert all users that it’s a typical broadcast, if there’s a need to be piped perform it then. If race conditions occur–queue the requests to view till the pipe is situated.

If a user is sitting alone in a room we do nothing, we don’t even connect the broadcast but say we did… lol