-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
preferTcp not honored #193
Comments
Thanks a lot. The documentation was ok, but the default values were wrong: Fixed in 2.0.14 and published. |
Same for
|
No, that's ok. The documentation, indeed, was wrong. Fixed now: https://mediasoup.org/documentation/mediasoup/api/#WebRtcTransport-MirroringOptions Thanks. |
Thanks!
…On Mon, Feb 26, 2018 at 3:20 PM Iñaki Baz Castillo ***@***.***> wrote:
No, that's ok. The documentation, indeed, was wrong. Fixed now:
https://mediasoup.org/documentation/mediasoup/api/#WebRtcTransport-MirroringOptions
Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#193 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABgVBvBfsqeYlN63NS_U4RQbNxk6Hg2Eks5tYyA1gaJpZM4STzee>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a room is created in mediasoup-client with
transportOptions: {preferTcp: true}
, the resulting remote candidate connection is shown in chrome://webrtc-internals/ as UDP. However, settingtransportOptions: {udp: false}
with the same SFU results in a working TCP connection.The text was updated successfully, but these errors were encountered: