Firefox pipeToRouter problems?

mediasoup libraries
2

I remember some issues in Firefox when creating two PeerConnections in the same website and the remote endpoint uses different DTLS certificates. So if you use two mediasoup Routers in different mediasoup Workers, each Worker will have its own random DTLS certificate.

NOTE: If “James” is not producing, then the sendTransport does not even connect ICE+DTLS to mediasoup. That happens once the first Producer (or DataProducer) is created. So this explains the issue if my above suspicion is true.

So:

  1. Ensure ICE and DTLS connects in both sendTransport and recvTransport when running Firefox in your failing scenario. This is critical, please don’t do bypass of this step. If I’m right one of those transports will fail at DTLS level.
  2. Create a TLS certificate and use it in your mediasoup Workers, so all Workers will use the same one and Firefox may not complain.
  3. If any of those is true, please comment here but also report the issue in the Firefox issue tracker.
1 Like