# After custom signalling, remote peers not able to consume/produce to mediasoup server running locally
**URL:** https://mediasoup.discourse.group/t/after-custom-signalling-remote-peers-not-able-to-consume-produce-to-mediasoup-server-running-locally/5053
**Category:** Deployment & Scalability
**Created:** [March 15, 2023, 1:06pm UTC](https://mediasoup.discourse.group/t/after-custom-signalling-remote-peers-not-able-to-consume-produce-to-mediasoup-server-running-locally/5053 "2023-03-15T13:06:28Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@vaibhavmuchandi](https://mediasoup.discourse.group/u/vaibhavmuchandi)
#### Post date: [March 15, 2023, 1:06pm UTC](https://mediasoup.discourse.group/t/after-custom-signalling-remote-peers-not-able-to-consume-produce-to-mediasoup-server-running-locally/5053/1 "2023-03-15T13:06:28Z")
Hi, I have a mediasoup-server running on my local machine
I have built a custom library to facilitate signalling through hole-punched network wherein a remote peer can signal to mediasoup-server running locally on my machine
As I can see that, I have all the transports opened
Producers and Consumers are being created as expected
But unfortunately they are not able to produce/consume
Is it because mediasoup cannot function behind NAT ? Or am I missing something over here ?
Here is my `chrome://webrtc-internals` where you can see that the inbound/outbound is empty
Where as when I connect 2 peers locally within my system, everything seems to be working fine
Is there a condition like we need a Non-NAT ip to get mediasoup to function correctly for remote peers ?
---
### Author:  [@ibc](https://mediasoup.discourse.group/u/ibc)
#### Post date: [March 15, 2023, 1:23pm UTC](https://mediasoup.discourse.group/t/after-custom-signalling-remote-peers-not-able-to-consume-produce-to-mediasoup-server-running-locally/5053/2 "2023-03-15T13:23:34Z")
> [@vaibhavmuchandi](#):
>
> Is it because mediasoup cannot function behind NAT ?
No, unless you redirect ports. Explained in the docs and in the FAQ in the website.
---
### Author:  [@vaibhavmuchandi](https://mediasoup.discourse.group/u/vaibhavmuchandi)
#### Post date: [March 20, 2023, 11:09am UTC](https://mediasoup.discourse.group/t/after-custom-signalling-remote-peers-not-able-to-consume-produce-to-mediasoup-server-running-locally/5053/3 "2023-03-20T11:09:09Z")
Is it because mediasoup implements ICE Lite ?
Is there a way in which we can initiate ICE Connections in a mediasoup-server ?
---
### Author:  [@vaibhavmuchandi](https://mediasoup.discourse.group/u/vaibhavmuchandi)
#### Post date: [March 27, 2023, 7:10am UTC](https://mediasoup.discourse.group/t/after-custom-signalling-remote-peers-not-able-to-consume-produce-to-mediasoup-server-running-locally/5053/4 "2023-03-27T07:10:58Z")
@ibc is it possible to disable ICE-Lite or have Mediasoup mediaserver configured with custom STUN/TURN ? How can one inititate a connection with a mediasoup ms running behind NAT without the going through the confusing process of having to open ports/do portforwarding ?
---
### Author:  [@ibc](https://mediasoup.discourse.group/u/ibc)
#### Post date: [March 27, 2023, 7:36am UTC](https://mediasoup.discourse.group/t/after-custom-signalling-remote-peers-not-able-to-consume-produce-to-mediasoup-server-running-locally/5053/5 "2023-03-27T07:36:33Z")
No, it’s not possible. mediasoup is ICE-Lite and must run with public IPs or port redirection. The docs clearly say it.