291–293 of 293 posts
Earlier quoted context omitted.
jitsi has dedicated apps for mobile https://jitsi.org/downloads/
Right. But I don’t want to have to tell a client to download an app. I’d rather they just go to a url like they do on an iPad. Not sure what the difference in browsers is between them, but I can’t imagine it’s much.
Earlier quoted context omitted.
> like most videoconferencing Well, if there's only 2, maybe 3 of you – anything beyond that is going to use a server to host the call for reliability.
> Well, if there's only 2, maybe 3 of you... Do you mean for more than 3 - the call/video is routed through the server and would consume server bandwidth? If so how is jitsi paying for all this if it is free?
Also easy to skin and deploy - we setup a custom branded instance for our customers to use during the pandemic within a couple of days: https://meet.brring.com/ It’s rather incredible what it can do: * SIP gateway to support inbound telephony dial in * Meeting recording * Auto scaling of the video bridges to dynamically handle load * Native iOS, Android and even Apple Watch clients All free, all open source. The inst…
I also deployed a Jitsi instance and was surprised how easy it was. I have two questions for you: 1. Do you see high CPU usage when there are multiple conferences with a few participants happening simultaneously? 2. How did you set up conference recording? I know Jibri exists but the installation instructions are quite confusing. It seems you need a VM per conference you want to record. Is that the case?
2. We did not on this instance but we did using their Docker instance which was very straightforward to setup: https://github.com/jitsi/docker-jitsi-meet#jitsi-broadcastin...
I don’t believe it needs a VM per conference - maybe a ffmpeg process per instance?
Here's the Jitsi architecture which best I can tell shows JIBRI (recording part) as a separate, single container: https://i.imgur.com/oDSRzF4.png
