Missing inbound-rtc in consumer

mediasoup libraries
1

Hello

I am having issue’s with consuming a producer and i dont know why. Code wise everything seems fine.

When i produce, i can see that the produce event on the send transport is called, the signalling to the server afterwards is also called and i can create consumers for all current peers.

And on the frontend the peers can get the “new consumer” signalling and local state is updated.

The problem is that the track from the consumer is blank(i cant see video nor hear audio) and when i log the consumer object and inspect the track, i see its muted. I did further investigation and can see from the consumer stats that there are no inbound-rtc.

My setup is running on an ec2 instance, with dedicated tcp and udp ports enabled, I also use a an announcedIp set to my public ip address.

I dont know what i am missing. I will appreciate any pointers.

2

If not done already, try inspecting the output logs of both the server and client for any error or warning logged by Mediasoup.

3

I dont get any errors from mediasoup either on the client /server side. But one thing i also noticed from the chrome://webrtc-internals is that on getTransceiver the sender also has empty track

4

I finally solved it. This(how to configure mediasoup server api in ec2 aws - #4 by nazar-pc)
gave me a clue of what could be wrong as it was also running on an ec2 instance.

What did I change?

  • I changed my upd port from a single port to a range of ports. (Careful if you are running docker as opening too many port range can stall startup)

  • I removed the rtcMaxPort on my workers setting as they are also deprecated. My port setting in my webRtcTransportOptions was also outside the bounds of this defined rtxMax and rtxMax Ports. This is what i believe is the real reason for my troubles.

  • I changed my webRtcTransportOptions listenIp property to listenInfos as listenIp is now deprecated(Not sure this is a problem as listenIp is still in the docs so I assume still currently supported)

  • I replaced the singular port in my listenIp(now listenInfos) property of the webRtcTransport to use the same port ranges I had opened.

Took me the whole day yesterday. But happy its finally sorted. Phew!

5

It would be good to see how the communication between your client and server is setup. If it would not be possible to share snippets of the code then ensure that your setup follows the procedure outline here Communication Between Client and Server

6

I am not sure if my post wasnt clear. I am saying i solved my issue :smiley:. I simply shared what i did to get it solved, and the post that helped me narrow down the problem. Hopefully someone else can find it useful if they get into a similar situation.

7

Ah I see, my bad. I had this page still open on the browser and didn’t get the refreshed update. Good to know you sorted it out.