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

is licode an MCU or an SFU #518

Closed
nikhilrayaprolu opened this Issue Aug 7, 2016 · 7 comments

Comments

Projects
None yet
5 participants
@nikhilrayaprolu

nikhilrayaprolu commented Aug 7, 2016

I have seen that SFU is more scalable than an MCU. even many other MCU based projects have implemented their system as an SFU( intel webrtc) . is licode an MCU or an SFU. if not an SFU ,do we have plans to make it do the functionality of an SFU

@lodoyun

This comment has been minimized.

Show comment
Hide comment
@lodoyun

lodoyun Aug 10, 2016

Contributor

Erizo, the WebRTC core of Licode is an SFU. It does have minimal transcoding capabilities that we may expand on at some point but we avoid transcoding whenever we can.

Fun fact: when I last checked, the Intel WebRTC thing included a modified version of Licode

Contributor

lodoyun commented Aug 10, 2016

Erizo, the WebRTC core of Licode is an SFU. It does have minimal transcoding capabilities that we may expand on at some point but we avoid transcoding whenever we can.

Fun fact: when I last checked, the Intel WebRTC thing included a modified version of Licode

@lodoyun lodoyun closed this Aug 10, 2016

@nikhilrayaprolu

This comment has been minimized.

Show comment
Hide comment
@nikhilrayaprolu

nikhilrayaprolu Aug 10, 2016

@lodoyun if intel MCU are able to add transcode capabilities for our code,why aren't we not adding it for original licode. What is the reason we are avoiding it right now?

nikhilrayaprolu commented Aug 10, 2016

@lodoyun if intel MCU are able to add transcode capabilities for our code,why aren't we not adding it for original licode. What is the reason we are avoiding it right now?

@jnoring

This comment has been minimized.

Show comment
Hide comment
@jnoring

jnoring Aug 10, 2016

@nikhilrayaprolu an SFU is not "more scalable" than an MCU, depending on what you mean by "more scalable." The reasons for avoiding it is that it's not a clear win, but a huge tradeoff.

jnoring commented Aug 10, 2016

@nikhilrayaprolu an SFU is not "more scalable" than an MCU, depending on what you mean by "more scalable." The reasons for avoiding it is that it's not a clear win, but a huge tradeoff.

@sebastianfelipe

This comment has been minimized.

Show comment
Hide comment
@sebastianfelipe

sebastianfelipe Sep 28, 2017

Well, but it works as MCU if the conversation is not a P2P, in that case, when the room is P2P set to true, then the connection is a Mesh?

sebastianfelipe commented Sep 28, 2017

Well, but it works as MCU if the conversation is not a P2P, in that case, when the room is P2P set to true, then the connection is a Mesh?

@kekkokk

This comment has been minimized.

Show comment
Hide comment
@kekkokk

kekkokk Sep 29, 2017

Contributor

MCU = have transcoding capabilities.
SFU = only "clone" packets and delivers to every participant.

when a licode room is set to p2p, it uses a mesh config. like you said.
when it's not set in p2p it acts like an sfu

Contributor

kekkokk commented Sep 29, 2017

MCU = have transcoding capabilities.
SFU = only "clone" packets and delivers to every participant.

when a licode room is set to p2p, it uses a mesh config. like you said.
when it's not set in p2p it acts like an sfu

@sebastianfelipe

This comment has been minimized.

Show comment
Hide comment
@sebastianfelipe

sebastianfelipe Sep 30, 2017

Perfect! Thanks, but why is not possible to use the mute audio/video with P2P communication? I think that is a client decision/characteristic and not a server feature.

sebastianfelipe commented Sep 30, 2017

Perfect! Thanks, but why is not possible to use the mute audio/video with P2P communication? I think that is a client decision/characteristic and not a server feature.

@sebastianfelipe

This comment has been minimized.

Show comment
Hide comment
@sebastianfelipe

sebastianfelipe Oct 1, 2017

Due this, I'd like to know one thing more, using SFU or MCU connections, then the RTCPeerConnection API is not available anymore? or that uses it, but considering the server as a peer? And about the security channel, does the connection still use the DTLS and SRTP/SCTP protocols in the session protected layer using SFU/MCU or is just TLS? Thanks.

sebastianfelipe commented Oct 1, 2017

Due this, I'd like to know one thing more, using SFU or MCU connections, then the RTCPeerConnection API is not available anymore? or that uses it, but considering the server as a peer? And about the security channel, does the connection still use the DTLS and SRTP/SCTP protocols in the session protected layer using SFU/MCU or is just TLS? Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment