Lynckia (our WebRTC-based MCU and service) is now completely Open Source

[javier cerviño]

Hi,

For those who are looking for an open source MCU, we've recently open
all the source code of Lynckia. It's aimed to provide any kind of
media communication (audio, video and data) through the MCU in order
to forward/mix/transcode traffic between clients.

The URL is http://www.lynckia.com

You can also join our google group
(http://groups.google.com/group/lynckia) in order to ask any related
question, propose changes or join our community.

Cheers,
Javier.

[Mamadou]

Tried http://chotis2.dit.upm.es/.
Video freezing with 3 participants. Are you simulcasting the video
stream?

On Dec 5, 12:52 am, javier cerviño <jcerv...@dit.upm.es> wrote:
> Hi,
>
> For those who are looking for an open source MCU, we've recently open
> all the source code of Lynckia. It's aimed to provide any kind of
> media communication (audio, video and data) through the MCU in order
> to forward/mix/transcode traffic between clients.
>

> The URL ishttp://www.lynckia.com

[med...@gmail.com]

Hi all,

We will like to announce that starting from SVN revision 650, the
Medooze MCU implements all the required functionalities to support
WebRTC endpoints.

http://www.medooze.com/products/mcu/webrtc-support.aspx

This means that you can now you can add web participants using WebRTC
and sip over websockets to the same conference in which you already have
your SIP participants in. Each participant has it's own decoder/encoder,
so they can join with different video codecs (VP8/H264/H263) and they
will still be able to see each other. You can deploy directly the MCU
on a Mobicents Sip Servlet server or integrate with a SIP Server/Proxy
supporting SIP over websockets. On the client side, you can use any sip
over websocket client, like sipml5 or jssip.

I have also set up a small demo (working on chrome>=24) which is
available here:

http://c21medooze.cires21.com/mss-example/

Just click on "register" and "call"

Best regards
Medooze team

[Albert Abello]

just me getting this error? I cannot test it in your chotis2 demo page. Tried on local but is crashing the basicdemo

Uncaught Error in RoapOnJsep: Dazed and confused in state offer-sent, stopping here 

[Pedro Rodriguez]

Hi

I'm afraid chotis2 is not related to Medooze so it is not their fault :)

That demo is for www.lynckia.com, another MCU unrelated to this one.

As far as the error goes, the version currently deployed in chotis2 does not run with post 23 versions of chrome. We have the next version ready and you can see the source in the github repository: https://github.com/ging/lynckia

Cheers!

-- 

Pedro Rodriguez

--
 
 
 

[Albert Abello]

Sorry, just mistaked the thread ;)

So just running for 23chrome? will wait for newer implementations. 

Cheers

[Joao Barbosa]

Hi,

i have a doubt but it is more for the ErizoAPI..in the client side we can use the WebRTC API from Chrome and in the server the ErizoAPI? or do we have to use the Erizo controller in the client side?

Thanks

[Álvaro Alonso]

Hi Joao,

erizo (and its node.js wrapper erizoAPI) is the webRTC MCU that we have developed for Lynckia but you can also use it without the rest of the modules. You can find the documentation in the github page (http://github.com/ging/lynckia/tree/master/erizoAPI). Therefore you can use it with the webRTC API but you must take into account that erizo is compatible with ROAP.

If you have any doubt you can ask us in our lynckia mail list (lyn...@googlegroups.com).

Regards,

Álvaro

2013/2/3 Joao Barbosa <joao.b...@gmail.com>

--
 

---
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.

--

--

Álvaro

[Álvaro Alonso]

Hi Alexey,

we are working on transcoding and mixing the streams on the server side (in fact this work is in a branch of our repository "media"). However, in the stable version of Lynckia they are rendered one by one. About the video resolution it is also in our roadmap the possibility of configure it (specially now with the chrome version for Android) but by the moment Lynckia uses the resolution that Chrome configures by default. 

You can subscribe to our mail list (http://lynckia.com/community.html) to be update of the news. 

Best regards, 

Álvaro

2013/3/17 Alexey Rybalko <alexey....@gmail.com>

Hi, Álvaro!

Would you please put some details on media streams delivery : are they mixed on the server side or rendered one by one in the client context? What is the highest video resolution supported by your MCU.

kind regards,
Alexey


понедельник, 4 февраля 2013 г., 14:06:27 UTC+4 пользователь Álvaro Alonso написал:

Hi Joao,

erizo (and its node.js wrapper erizoAPI) is the webRTC MCU that we have developed for Lynckia but you can also use it without the rest of the modules. You can find the documentation in the github page (http://github.com/ging/lynckia/tree/master/erizoAPI). Therefore you can use it with the webRTC API but you must take into account that erizo is compatible with ROAP.

If you have any doubt you can ask us in our lynckia mail list (lyn...@googlegroups.com).

Regards,

Álvaro

--

 
---
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.
 
 

--

--

Álvaro

[Nikhil Agrawal]

Hi Alvaro,

Does the code on media branch working? If working then do I need to do any changes in code to run it or I can just run it as is like stable version?

[jillu sk]

Can we use WebRTC-based MCU services in Windows 8 store apps/Windows phone 8?

Can this api has Rest services and will support audio/video?

if supports how can we achieve it?

[Rahul]

Hi Alvaro,

I still see this below feature not implemented and still on branch ,please correct me if i am wrong .Do you guys have working copy of Media mixing feature in licode.

Thanks

/R

[Álvaro Alonso]

Hi,

mixing streams in server side is not in our roadmap right now. This is due to performance reasons. Licode is very oriented to the cloud and mixing streams in the MCU is very expensive in CPU terms. When you have a high number of users in a multivideoconference room a solution is to decrease the bandwidth of each stream (this feature is already implemented in Licode).

About the transcoding feature, it is already implemented in Licode and used when getting streams from external inputs such us cameras ips (RTSP streams).

I hope these answers help you. 

Best, 

Álvaro

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

[Jed]

If you try to join a conference with medooze through SIP that is not available, would one automatically be created?

[Sergio Garcia Murillo]

Hi Jed,

For medooze WebRTC  MCU issues better post here instead:

http://sourceforge.net/p/mcumediaserver/discussion/

Best regards
Sergio

--

[Anguo Yang]

hi, medooze has 2  versions, open source and commercial version, they are difference with each other.

在 2012年12月5日星期三UTC+8下午8时38分24秒，med...@gmail.com写道：

[Luca De Cicco]

I apologize in advance in the case this was asked before. Is Lynckia implementing a congestion control algo?

Best,

Luca

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

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

--

---
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-webrtc+unsubscribe@googlegroups.com.