# Anyone done server-to-server router pipe impl yet?

**URL:** <https://mediasoup.discourse.group/t/anyone-done-server-to-server-router-pipe-impl-yet/1349>\
**Category:** mediasoup libraries\
**Created:** [June 28, 2020, 4:40am UTC](https://mediasoup.discourse.group/t/anyone-done-server-to-server-router-pipe-impl-yet/1349 "2020-06-28T04:40:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cretz](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/cretz/32/566_2.png) [@cretz](https://mediasoup.discourse.group/u/cretz)\
**Post date:** [June 28, 2020, 4:40am UTC](https://mediasoup.discourse.group/t/anyone-done-server-to-server-router-pipe-impl-yet/1349/1 "2020-06-28T04:40:53Z")

</div>

From [https://mediasoup.org/documentation/v3/scalability/:](https://mediasoup.org/documentation/v3/scalability/:)

> It’s also perfectly possible to inter-communicate mediasoup routers running in different physical hosts. However, since mediasoup does not provide any signaling protocol, it’s up to the application to implement the required information exchange to accomplish with that goal. As a good reference, in order to pipe a producer into a router in a different host, the application should implement something similar to what the [router.pipeToRouter()](https://github.com/versatica/mediasoup/blob/v3/lib/Router.js#L538) method already does, but taking into account that in this case both routers are not co-located in the same host so network signaling is needed.

I am about to tackle this task for my use case, but before I started I was wondering if anyone had done this before? I am looking for any example code or any quirks. At first glance it doesn’t seem `pipeToRouter` impl is that difficult to signal params back and forth on…will report back if I hit snags or have code to share.

---

<div class="post-metadata">

**Author:** ![jmillan](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/jmillan/32/9_2.png) [@jmillan](https://mediasoup.discourse.group/u/jmillan)\
**Post date:** [June 30, 2020, 10:54am UTC](https://mediasoup.discourse.group/t/anyone-done-server-to-server-router-pipe-impl-yet/1349/2 "2020-06-30T10:54:45Z")

</div>

If you search in this forum for `pipeToRouter` you’ll already get plenty of entries.

---

<div class="post-metadata">

**Author:** ![gurupras](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/gurupras/32/738_2.png) [@gurupras](https://mediasoup.discourse.group/u/gurupras)\
**Post date:** [July 4, 2020, 1:15pm UTC](https://mediasoup.discourse.group/t/anyone-done-server-to-server-router-pipe-impl-yet/1349/3 "2020-07-04T13:15:35Z")

</div>

There are lots of corner cases to handle ☹  
Here’s one I recently worked on: lets say one of the nodes goes down. When you bring it back up, you need to clear out all the previous producers/consumers and close the remote pipeTransports.

---

<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:** [July 9, 2020, 11:25am UTC](https://mediasoup.discourse.group/t/anyone-done-server-to-server-router-pipe-impl-yet/1349/4 "2020-07-09T11:25:50Z")

</div>

It’s up to you how to monitor whether nodes are up and down. That’s inter-server communication stuff. Not related to mediasoup.