Multiparty conference (3-way video)

[Riccardo Tresoldi]

I'm interested to know if now WebRTC, Chrome and Firefox implementation, is albe to create multiparty calls. (like 3-way talk or a conference).

Is it?

If it is able to do this, someone can explain how is the workflow of a conference?

(For example: this is the shema for p2p call (http://www.webrtc.org/reference/native-apis/WebRTCNativeAPIsDocument%20%281%29.png), I need something similar for 3-way calls)

[Philipp Hancke]

http://www.html5rocks.com/en/tutorials/webrtc/infrastructure/#beyond-one-to-one-multi-party-webrtc explains this. For a small number of participants the "full-mesh" approach scales well enough.

--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Riccardo Tresoldi]

Thanks a lot! That's really helpful for me!

"Full-mesh" looks more like a workaround then a solution ;)

Are there a more "technically correct" solution in W3C documents? Do they already design this use case?

[Alexandre GOUAILLARD]

"Full-mesh" looks more like a workaround then a solution ;)

Beauty is in the eye of the beholder :-)

 

Are there a more "technically correct" solution in W3C documents?

No.

 

Do they already design this use case?

No. This is a use case for applications to handle, not for the webRTC API to handle. PeerConnection API is really 1-1. Whatever topology of connection of users you want on top of that is up to you and your application. 

 

Il giorno giovedì 27 febbraio 2014 17:37:52 UTC+1, Philipp Hancke ha scritto:

http://www.html5rocks.com/en/tutorials/webrtc/infrastructure/#beyond-one-to-one-multi-party-webrtc explains this. For a small number of participants the "full-mesh" approach scales well enough.

On Thu, Feb 27, 2014 at 5:29 PM, Riccardo Tresoldi <riky...@gmail.com> wrote:

I'm interested to know if now WebRTC, Chrome and Firefox implementation, is albe to create multiparty calls. (like 3-way talk or a conference).

Is it?

If it is able to do this, someone can explain how is the workflow of a conference?

(For example: this is the shema for p2p call (http://www.webrtc.org/reference/native-apis/WebRTCNativeAPIsDocument%20%281%29.png), I need something similar for 3-way calls)

--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.

To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Alex. Gouaillard, PhD, PhD, MBA

------------------------------------------------------------------------------------

CTO - Temasys Communications, S'pore / Mountain View

President - CoSMo Software, Cambridge, MA

------------------------------------------------------------------------------------

sg.linkedin.com/agouaillard

• 
  

[@amiteshawa]

you can refer here: http://www.slideshare.net/amiteshawa/setup-ephemeral-password 

you can fork sample code here: https://github.com/amiteshawa/learn-rtc 

[Alexandre GOUAILLARD]

@amitesh,

Those are great slides, and introduce what is used by a lot of vendors out there.

That being said, you will have to admit that, **with respect to W3C specs** (which is the scope of riccardo's question), the choice of web socket for the signaling transport, and the set up of TURN server the way you did, if only, are arbitrary.

@riccardo,

I think asking the question in the scope of the w3c specs is not the right thing to do. With that in mind, both philipp ad amitesh answers are as-good-as-possible answers to your problem.

The average size (in number of users) of video conference is 3.4. Some even say that the main use case for webrtc is 1-1 (http://bloggeek.me/5-things-webrtc/). Full mesh approaches can handle easily 10 people on desktop and 4 on mobile. Are you sure you need more than that?

Again, there are a lot of API/SDK out there that implement variations of the concept presented in amitesh slides (the full mesh concept philipp pointed you to), and you just have to go out, do your homework and some shopping around :-) 

HTH

Alex.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Riccardo Tresoldi]

I still have not done any tests, but my doubt is in the number of stream that have to be sent through the web.

With a full-mesh solution with 4 people there's 6 peerCnnection, and for each connection there's 2 audio/video stream... Is 12 stream for 4 people in a conversation...

I think that another problem could be synchronization between all the peers. no?

Anyway... my question was just for educational purposes... ;)

Thanks @amiteshawa! ;)

[Lorenzo Miniero]

Riccardo,

you're right, full mesh can be kind of overkill in some scenarios, especially as numbers increase. You may want to have a look at some WebRTC MCUs out there. Just FYI, I recently published a gateway that can be used as an MCU as well, in case you want to check whether it may suit your purposes: http://janus.conf.meetecho.com/ but there are other good alternatives as well (e.g. Licode).

Lorenzo

[Riccardo Tresoldi]

Thanks a lot Lorenzo! ;)

I'm already working around a server-side solution for multiparty conference with AddLive (http://addlive.com)