If you use the jitsi.org service on the main website for conferencing, there is a tool in the menu allowing people to record. Unfortunately (and rather strangely!) it prompts you to login to DropBox (proprietary software) in order to do so, without any option for a custom alternative...
@nebulon I've always thought it was coming from the sounding of running apps in the cloud. And so that is why one needs its apps to be cloud run(ed), or even cloud r on whatever that sounds loudly pronounced in some part of the world. 🙂
User authentication (which JWT tokens will do in this case) is currently not possible to customize and the current package does not yet support JWT tokens.
Regarding the config files, The ones used are symlinked into /etc and can be found in /run. Those however are recreated on every app restart so currently no permanent customizations can be made to those.
@jdaviescoates just for information. Jitsi will do a direct p2p connection with two meeting participants. Once a 3rd person joins, it will use an SFU. So the connectivity specifics are quite different between 2 and more meeting participants.
@ei8fdb did you get it working? I have had that port open since installation (I also self host) but mine has no audio or video either. Similar problem I have to audio calls through matrix... It all works fine on the same network but not if devices are on different networks and as far as I can tell the logs show everything working fine.
Hi @ericdrgn I was waiting to have the time to test this morning.
I have tested just now:
server (8GB memory & 30% CPU dedicated) on home internet IP
clientA (laptop, browser) on external WiFi network
clientB (mobile android device, jitsi client) on mobile network
I did have video, and audio from both clients.
If you try some calls and grep for the messages I got? You can see them in the paste link.
@MooCloud_Matt@luckow my #1 question: do we know if Cloudron authentication will be implemented? I'd imagine some level of access must be public for none authorized users to join but what about spam/malicious users making rooms?
Ah that is actually not a jitsi issue, but a platform bug. I have seen that sometimes during e2e tests, but so far I wasn't able to reproduce this reliably. As you mentioned a retry usually works then. Something with docker recycling container IPs.