Plain Transport Custom RTCP Port

[ezioda004]

Feature Request

When we create PlainTransport with rtcpMux false, then the transport uses 2 ports. One for RTP and the other for RTCP. While creating we can pass the port to router.createPlainTransport(), however, the RTCP port is selected from the worker's port range. I'm requesting an option to pass down a custom RTCP port to router.createPlainTransport(), so the application layer can manage this port. In our app, we're already managing pipe transport ports and with the addition of plain transport, we're only able to manage RTP ports and not RTCP.

[ibc]

PR done here: #1099

However, note that such a PR targets flatbuffers branch which has an ongoing PR #1064. So this feature will be in v3 once both PRs are merged.

[ezioda004]

This is great, however, I was expecting an option like rtcpPort like we have a port option in PlainTransportOptions. Would it make sense to add this option alongside rtcpListenInfo?

[ibc]

This is great, however, I was expecting an option like rtcpPort like we have a port option in PlainTransportOptions. Would it make sense to add this option alongside rtcpListenInfo?

Definitely not. ListenInfo is the way to go once flatbuffers branch is merged in v3, and ListenIp will be deprecated. Some for port option in every router.createXxxTransport() API.

[ezioda004]

Definitely not. ListenInfo is the way to go once flatbuffers branch is merged in v3, and ListenIp will be deprecated. Some for port option in every router.createXxxTransport() API.

Ok, so listenInfo and now rtcpListeninfo will replace listenIp, port. Understood.

[ibc]

Will not replace because the former options will still be available to not break backwards compatibility, but I don't want to add already deprecated new options.

[ibc]

This was done long ago.