In order to fix issues where the Receiver was using default STUN servers (google's), a new approach was needed to acquire the stream's "extra" property/metadata prior to connecting following previous PR for #185.
In this PR, we create a connection prior to the actual media (audio/video) connection just to fetch the stream metadata prior to making our usual/normal connection. This allows us to know whether to use TURN servers on the actual media connection since we'll have the isP2POnly property of RTCMultiConnection#extra from the "pre-connection".
In order to fix issues where the Receiver was using default STUN servers (google's), a new approach was needed to acquire the stream's "extra" property/metadata prior to connecting following previous PR for #185.
In this PR, we create a connection prior to the actual media (audio/video) connection just to fetch the stream metadata prior to making our usual/normal connection. This allows us to know whether to use TURN servers on the actual media connection since we'll have the
isP2POnlyproperty ofRTCMultiConnection#extrafrom the "pre-connection".