mediasoup v3.6.29 => listenIps failure

79 views
Skip to first unread message

Tommy Grimes

unread,
Dec 28, 2020, 10:25:24 PM12/28/20
to mediasoup
I have come across an issue in my configurations that I cannot seem to resolve. Currently deployed with a digital ocean droplet. I placed my private ip string in the "ip" key under the object array of listenIps. As well as my public IPV4 ip address under the announced ip. Even switched them at one point thinking my configurations were wrong.

Currently there is no feed coming via audio and video. However the transport(s) seem to be logging properly. Below specifically is my configuration for the router webRtcTransportation.

webRtcTransport: {
listenIps: [ { ip:PRIVATE IP STRING,    announcedIp: 159.203.159.129 } ],
enableUdp: true,
enableTcp: true,
preferUdp: true,
maxIncomingBitrate: 1500000,
initialAvailableOutgoingBitrate: 1000000,
}

localhost setup works fine.I have searched the documentation and have come to the understanding that my listenIps might not be configured properly. Stuck and very frustrated. I am wondering if I am missing something. Any help greatly appreciated.


Tommy Grimes

unread,
Dec 28, 2020, 11:44:38 PM12/28/20
to mediasoup

My ifconfig


eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 134.209.117.193  netmask 255.255.240.0  broadcast 134.209.127.255

        inet6 fe80::dc58:86ff:feac:7ec4  prefixlen 64  scopeid 0x20<link>

        ether de:58:86:ac:7e:c4  txqueuelen 1000  (Ethernet)

        RX packets 9514227  bytes 7660387197 (7.6 GB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 11414044  bytes 8817720630 (8.8 GB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 10.116.0.2  netmask 255.255.240.0  broadcast 10.116.15.255

        inet6 fe80::18f2:8fff:fe05:7903  prefixlen 64  scopeid 0x20<link>

        ether 1a:f2:8f:05:79:03  txqueuelen 1000  (Ethernet)

        RX packets 5943  bytes 278494 (278.4 KB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 1052  bytes 73736 (73.7 KB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 1000  (Local Loopback)

        RX packets 859093  bytes 7615584218 (7.6 GB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 859093  bytes 7615584218 (7.6 GB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Amit Madabhavi

unread,
Dec 29, 2020, 1:46:12 AM12/29/20
to medi...@googlegroups.com
Hi,

Instead of providing the private ip string, please provide the public ip of the droplet in webrtctransport options ip key. And make sure to open the ports for both udp and tcp.

Regards,
Amit M

--
mediasoup
Cutting Edge WebRTC Video Conferencing
 
https://mediasoup.org
 
NOTE: This group is deprecated. Use the mediasoup Discourse Group instead:
 
https://mediasoup.discourse.group
---
You received this message because you are subscribed to the Google Groups "mediasoup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mediasoup+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mediasoup/aef8855d-29a1-4495-b069-fcd401cb7495n%40googlegroups.com.

Tommy Grimes

unread,
Dec 29, 2020, 11:07:54 AM12/29/20
to mediasoup
Hi Amit. Much appreciated for your reply. As you said, I configured the the listenIps as follows:

listenIps: [
{ ip: '134.209.117.193', announcedIp: null }
]

The '134...' is my public IPV4 address (My droplet IP)

I was under the assumption that I also needed an announced IP.

To further add, I do already use socket.io within my app, which works fine on production. Is it safe to assume that since I am able to send and receive packets via socket.io that my udp and tcp are allowed and open?

Amit Madabhavi

unread,
Dec 29, 2020, 2:02:13 PM12/29/20
to medi...@googlegroups.com
Hi,

Socket io connection should be established over port 443. But the actual media data flows on these ports which were given when u create the worker. So make sure the ports you gave as rtcmin and rtcmax ports are open. Also you have to set both the announcedip and listenip to the public ip address of your digital ocean box.

Webrtc sends the data with dtls. So you dont need to worry about security aspect when keeping the ports open. Hacker may hit your port but he would not be able to do anything much.

Regards,
Amit M

Tommy Grimes

unread,
Dec 29, 2020, 3:25:54 PM12/29/20
to mediasoup
To Amit

I wanted to say that your instructions, along with reconfiguring my ufw firewall did the trick. 

I am sending you good karma. Your insight was a selfless act. Thank you truly.

- Tommy
Reply all
Reply to author
Forward
0 new messages