![]() ![]() For example: I just created an empty Asp.Net MVC web application, changed the MVC router, added index.html and libs and it worked. You can use the libs to start jitsi-meet as you please. Replace the virtual script includes to normal html includes and point them to your libs I didn't manage to get them through PR, but I think I covered all of the changes in this Issue: Ĭhange the config.js to point to your Openfire installation (I cheated here a bit and installed the OFMeet plugin to Openfire, opened the Jitsi-Meet window and copied config.js contents through Developer Tools - set up to connect to openfire) Clone the repository, install the dependencies and make some minor changes to to actually build the sources on windows. To build the libs, you will need NodeJS and Python27 installed (I will assume you know how to use NodeJS). Install Jitsi Focus Conference plugin (Jifoco) Install Openfire, most values stay default or are based on your configuration. You can than go the embarrassingly simple way (install Openfire Meetings plugin through Openfire administration and you have jitsi-meet running), or the adventurous and not-that-simple way (built from sources): You can't use Prosody, so we will switch to Openfire. Especially Mike Kuketz has some advanced configuration tips like disabling third party requests with “disableThirdPartyRequests: true” or limiting the number of video streams and such.I am late to answer, but I want to share some info with other people trying to run jitsi-meet on Windows. The other URLs above are helpful as well and more elaborate then my few lines here. There tons of config options where you can easily make mistakes, but watching your logs and your debug console should really help you in sorting out these kind of errors. etc/jitsi/jicofo/sip-communicator.properties: there might be stupid errors like (in my case) wrong hostnames like “” (a double dot in the domain), but you can spot those easily in the debug console of your browser. It’s easier to solve one issue after the other and make one config change at a time instead of needing to make changes in several places. Using the port in the config might be a quick way to test whether or not your config is working. Of course you can also take care that your bosh requests get forwarded by your webserver as reverse proxy. In the above config snippet one of the issues solved was to add the port to the bosh setting. Jitsi config is like this for me with short domains (/etc/jitsi/meet/): var config = , Maybe not all of the above lines are necessary, but this works for me. Just make just that your config is consistent with what Jitsi Meet wants to connect to. If you prefer conference instead of chat, then you shouldn’t be affected by this. ![]() There is more config that needs to be done, but one of the XMPP Failures I spotted from debug console in Firefox was that it tried to connect to while I prefer to use for its brevity. # Avoid buggy clients to make their bookmarks public Max_items_node: 5000 # For Jappix this must be set to 1000000 Host: yourIP # Your coturn's public address. Of course you also need to add some config to your ejabberd.yml: host_config: That way I catched some XMPP Failures and saw that it tries to connect to some components where the DNS records were missing: meet IN A yourIP If something is not working with Jitsi Meet, it helps to not watch the log files only, but also to open the Debug Console in your web browser. It was set to jre-7, but I guess this was from years ago when I ran OpenFire as XMPP server. * 0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1111 auto modeġ /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1111 manual modeĢ /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual modeģ /usr/lib/jvm/jre-7-oracle-圆4/bin/java 316 manual mode One of the first issues I stumpled across was that my Java was too old, but this can be quickly solved by update-alternatives: There are 3 choices for the alternative java (providing /usr/bin/java). This is not a step-by-step description, but anyway… here we go with some links: As always, it’s sometimes difficult to find the correct/best non-official documentation or how-to, so I try to describe what helped me in configuring Jitsi Meet with ejabberd as XMPP server and my own coturn STUN/TURN server… Only thing is that you can’t follow the official Jitsi documentation when you are not using Prosody but instead e.g. ![]() But it’s basically irrelevant which XMPP you want to use. While Jitsi itself uses Prosody as XMPP and their docs only covers that one. You can see the network overview in the docs. But there are Debian packages provided by Jitsi itself. One of the solutions is Jitsi Meet, which is NOT packaged in Debian. those people that try to coordinate with coworkers while in home office. Since the more or less global lockdown caused by Covid-19 there was a lot talk about video conferencing solutions that can be used for e.g. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |