Setup help

[Rafael Gawenda]

Hi

I'm trying to integrate meedoze in an existing and working setup, but I can't correctly link between media-server-node and media-server-client-js.

I've spent a couple of days reading documentation, code, samples, demo (to the point of submitting a couple of typo PR), but in the client readme talks about a TransactionManager in the server, and I'm not seeing much documentation on the server(manual).

I'm not using any framework in either side, and my current setup includes websocket connections (I'm opening an empty one directly only for medooze), but I'm not using the same websocket implementation in node (websocket/ws instead of theturtle32/websocket).

I've previously achieved my goal (SFU) by usign node-wrtc, but it's neither stable nor efficient.

Any hint will be highly appreciated

[Sergio Garcia Murillo]

You can see an example of the how to integrate the media server with the client sdk here:

https://github.com/medooze/test-server/blob/master/lib/PartyLine.js

It is a single room sfu kind of demo, but should be enough as a starting point.

Best regards

Sergio

--
You received this message because you are subscribed to the Google Groups "medooze" group.
To unsubscribe from this group and stop receiving emails from it, send an email to medooze+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/medooze/60760dd5-c129-4656-93e9-2c00399d00dbn%40googlegroups.com.

[Rafael Gawenda]

Thank you  Sergio.

Been there, but maybe my problem is about the underlying websocket implementarion.
The sample websocket server emits a protocol "request" and the module I user doesn't have that event. I'm currently RTFM there about a possible request.accept in the upgrade event, but at that point what I've is a TLSSocket object and not a WebSocket one

[Rafael Gawenda]

Or maybe, as I'll use a dedicated websocket, I could use both implementations at my server side

[Sergio Garcia Murillo]

You don't need to use the theturtle32/websocket implementation, for the server you just need to pass a TransactionManager object, which just expects a "transport" object with a simple alpi, basically an onmessage event handler and a send method. Sould work with twebsocket/ws 

https://github.com/medooze/transaction-manager/blob/master/test/test.js

Best regards

Sergio

To view this discussion on the web visit https://groups.google.com/d/msgid/medooze/f9562871-8d95-4cab-ab9e-59188645d205n%40googlegroups.com.

[Rafael Gawenda]

Ok, I got the managed peerConnection, after patching semantic-sdp/lib/SDPInfo.js which was throwing me an exception.

I've submitted a PR to review

Thank you!

[Rafael Gawenda]

Hi

Just an update. I got everything working and integrated replacing my previous setup. Basically I'm now using both node websocket libraries, but replaced SimplePeer and wrtc with medooze, and removed a turn server. Code size and complexity is about the same, but resource (CPU) and connection speed are now much better (It seems wrtc was usable for a simple stream, but not for a SFU, also I found it highly inestable for production).

[Sergio Garcia Murillo]

That is great news!

Glad you made it work

Sergio

To view this discussion on the web visit https://groups.google.com/d/msgid/medooze/13d44a25-3be8-4be9-8fd1-7d379903afc3n%40googlegroups.com.