Mediasoup's WebRtcServer concerning firewall settings and port binding.

Deployment & Scalability
5

Yeah,

In conclusion in the scenario where i employing 3 instances of WebRtcServer, each configured with distinct listenInfos to operate on separate UDP/TCP ports, for instance

[4/4/2024, 12:05:23:444] [Server] Create a WebRtcServer {
  worker_pid: 43294,
  webRtcServerOptions: {
    listenInfos: [
      {
        protocol: 'udp',
        ip: '0.0.0.0',
        announcedAddress: 'Server Ipv4',
        port: 44444
      },
      {
        protocol: 'tcp',
        ip: '0.0.0.0',
        announcedAddress: 'Server Ipv4',
        port: 44444
      }
    ]
  }
}
[4/4/2024, 12:05:23:465] [Server] Create a WebRtcServer {
  worker_pid: 43295,
  webRtcServerOptions: {
    listenInfos: [
      {
        protocol: 'udp',
        ip: '0.0.0.0',
        announcedAddress: 'Server Ipv4',
        port: 44445
      },
      {
        protocol: 'tcp',
        ip: '0.0.0.0',
        announcedAddress: 'Server Ipv4',
        port: 44445
      }
    ]
  }
}
[4/4/2024, 12:05:23:483] [Server] Create a WebRtcServer {
  worker_pid: 43296,
  webRtcServerOptions: {
    listenInfos: [
      {
        protocol: 'udp',
        ip: '0.0.0.0',
        announcedAddress: 'Server Ipv4',
        port: 44446
      },
      {
        protocol: 'tcp',
        ip: '0.0.0.0',
        announcedAddress: 'Server Ipv4',
        port: 44446
      }
    ]
  }
}

and i pass them to the createWebRtcTransport(), I need only to guarantee that these 3 ports (44444,44445,44446 UDP/TCP) remain unblocked by the firewall and are available for binding. Each WebRtcServer instance abstracts the management of RTP and RTCP traffic, handling it internally, without the need to use the rtcMinPort-rtcMaxPort port ranges.