WebRtcServer may select the wrong WebRtcTransport when the endpoint restricts the port range

[ybybwdwd]

Bug Report

Your environment

• Operating system: linux
• mediasoup worker: latest

Issue description

When the endpoint port range is restricted, new STUN packets of transportA may be sent from the old transport tuple of transportB, causing the WebRtcServer to select an incorrect WebRtcTransport based on the TransportTuple，then ice response 401

[ibc]

I'm afraid we need much more info and details and evidences to handle this issue report.

mediasoup creates a hash with the transport source ip:port and destination ip:port. It should be extremely hard for two hashes to collide.