Is there a way to use client-side mediasoup only, which means I don’t want to use server-side mediasoup and want to use my own signaling server logic. I have trouble installing server-side mediasoup, and I don’t want to spend time on configuring the computer to make it work. Running the server-side mediasoup in docker container is also a little bothering, and actually I don’t need the functions of server-side mediasoup as I only need one server node to run my service.
This question makes no sense at all:
-
mediasoup and mediasoup-client do NOT provide any signaling stuff. Rule #1 of mediasoup v3.
-
What do you want mediasoup-client for if it does not communicate with a mediasoup server?
What I want is a library, which encapsulates webrtc, runs on client-side and supply simple APIs. I think it’s possible for a webrtc library, using which the server just sends messages and manages users.
What you are looking for is not mediasoup-client.
If i understood correctly you’re describing regular webrtc, peer to peer. Not an SFU.
An SFU without server-side handling doesn’t make any sense.
1 Like