mediasoup 3.17.0 released

Announcements
1

mediasoup 3.17.0 has been released. It comes with a new option exposeInternalIp in TransportListenInfo object:

exposeInternalIp: In transports with ICE candidates, this field determines whether to also expose an ICE candidate with the IP of the ip field when announcedAddress is given.

Usage example:

const webRtcServer = await router.createWebRtcServer({
  listenInfos: [
    {
      protocol: 'udp',
      ip: '192.168.1.101',
      announcedAddress: '9.8.7.6',
      exposeInternalIp: true,
      port: 55555,
    },
  ],
});

Related PR: `ListenInfo`: Add `exposeInternalIp` field by ibc · Pull Request #1583 · versatica/mediasoup · GitHub

3 Likes
2

I honestly like this, some further context may help with the documentation.

exposeInternalIp:

When using ICE candidates and an announcedAddress is set (e.g., a public IP or domain), this option controls whether to also include the internal/local IP address in the candidate list.

  • If true, both the local IP and announced address are advertised.

  • If false, only the announced address is used.

This can improve connection options for peers on the same local network. However, remote peers might receive internal IPs they cannot use, so disabling this can reduce unnecessary connection attempts.

—
Curious as I know this isn’t ideal solution (github); will this at all conflict with pipe transports or treat those the same still?

3

Thanks, changes pushed.

This option doesn’t affect plain or pipe transports because there are no ICE candidates in those transports so setting that option to true has no effect.

4

Thank you for clarification! I thought so was just being sure.

5

This topic was automatically closed after 2 days. New replies are no longer allowed.