There is a lot of discussion related to Talk limitations and other community members recommending Jitsi (which is also built on WebRTC and heavily used by projects such as Matrix, Rocket.chat, Comcast Video service, etc.). The project is also interesting in how it supports Etherpad, used by the Ownpad app, and XMPP. Anyone can jump on or even create a registration-free video call here at: https://meet.jit.si/nextcloud
13 Likes
I am huge fan of Jitsi too.
I stopped using Talk because of a huge latence when sending a write with a Nginx back server and a poor video call quality (even with a dedicated Stun/turn server)
Since the Covid-19 i use Jitsi and it’s great.
8 Likes
https://jitsi.org is really cool.
2 Likes
It would be cool if someone would build a Jitsi integration.
15 Likes
i don’t think that jitsi would get intregrated into talk… why would talk ppl would want to do that? to ruin their businessmodel?
so i think it will be an app of its on… whenever it will come. and yes… i think it would be great to have it integrated into NC as an app of it’s own.
so a +1 from my side 
I think the better is to have a Matrix App for Nextcloud because Matrix can embrase Jitsi.
5 Likes
Why would that be better?
Matrix uses Jitsi for video and audio calling. So, implementing either could help with the other. 
5 Likes
Interfacing NC talk with SIP would enable Jitsi integration and also many other systems.
Asterisk provides a WebRTC service and SIP - this may be the shortest route. With Asterisk <-> NC Talk, you would have access to Jitsi, PSTN, SIP services plus more.
If anyone is interested in working on the NC Talk side, I can provision a test Asterisk and Jitsi to test this against (and of course publish the method).
[Edit] Jitsi SIP seems to only currently support audio, not video so the WebRTC may be the way to go. Thought also must be put to what is shared from Jitsi - if it is a conference, do all streams get sent to Talk, or a composite view of the participants, is this the speaker view or tile view etc etc.
3 Likes
Jitsi is a great tool for communication - if it was somehow possible to integrate the server into a nextcloud environment, that would be awsome.
Are there any chances that can be done?
I just tried out Talk and it doesn’t work at all for me. I can see other people’s names, but I cannot see nor hear them.
Please move your support request to a new post, so we can keep this thread about Jitsi. Thanks!
@anon75456558
even better… @nextmax could use the search function … to find his answers already answered a dozen times.
Just wrote a bot: https://github.com/pojntfx/nextcloud-talk-jitsi-bot
Pretty simple to use; add the bot to the chat, type #videochat and get a link to a Jitsi meeting.
2 Likes
I don’t use docker and i run my own Jitsi meet server. How can i use this “bot”?
Cool, I like how you use meet.jit.so for this. Did you base it off this Telegram bot for Talk?
You all want your own cloud? But rely on an external service provider, like Jitsi.me?
I have not seen a single person mention that domain.
Jitsi is no more of an external provider than Nextcloud itself: Both code fully open source software that you are welcome to run on your own hardware in any capacity.
1 Like
Alright, if someone is still interested, i just rewrote the Jitsi Nextcloud Talk bot in Go, which should make everything much faster and simpler to deploy: https://github.com/pojntfx/nextcloud-talk-jitsi-bot
I even did a short video (in German) explaining the usage: https://www.youtube.com/watch?v=ahwGVSfwssM
Maybe this could be a good intermediary solution; if you want to build your own chatbots etc., the Nextcloud Talk Jitsi Bot provides a simple framework to do so if you know Golang.
10 Likes
I’d of course recommend you use Docker or some other CRI-compatible software (it’s 2020 after all), but if you don’t want to use it - just take a look at the Dockerfile, it explains how to build an ELF binary. You should by fine by creating say a systemd service and setting the env variables as explained in the README (the -e flags)
What’s the point in having to use docker because it’s 2020? Did I miss something?
If you run a production server and care about security, you will probably not use docker, as it still has to run as root (rootless mode isn’t yet a native and easy to use function in 2020).
Don’t be deceived by the all is easy promises. Docker can even complicate things quite a bit under some circumstances.
2 Likes