Skip to content
Videoconferencing based on WebRTC and Janus Gateway with an UI inspired by Google Hangouts
JavaScript HTML CSS Ruby Shell
Branch: master
Clone or download
ancorgs Merge pull request #217 from jangouts/v047
Version 0.4.7 including final touches
Latest commit 28e2132 Nov 20, 2017
Type Name Latest commit message Commit time
Failed to load latest commit information.
doc Improve Jul 21, 2017
e2e Initial commit (gulp, bower and boilerplate) Apr 13, 2015
gulp Remove unused karma package Nov 17, 2017
provisioning Vagrant uses openSUSE Leap 42.1 instead of 13.2 May 5, 2016
src Fix another spurious on quick logout Nov 20, 2017
.bowerrc Initial commit (gulp, bower and boilerplate) Apr 13, 2015
.editorconfig Initial commit (gulp, bower and boilerplate) Apr 13, 2015
.gitignore Update .gitignore Nov 14, 2017
.jshintrc Configuration is loaded synchronously Dec 23, 2015
.yo-rc.json Initial commit (gulp, bower and boilerplate) Apr 13, 2015 Use ws:// instead of http:// in deployment guide Jan 3, 2016 Update documentation Dec 23, 2015
LICENSE-artwork.txt WIP: first prototype of Notifier service Sep 11, 2015
LICENSE.txt Improved README file. Added LICENSE.txt May 5, 2015 Add documentation about the Callstats plugin Nov 14, 2017 Update documentation Dec 23, 2015
Vagrantfile.sample Vagrant uses openSUSE Leap 42.1 instead of 13.2 May 5, 2016
bower.json Version 0.4.7 Nov 20, 2017
browsers.txt Added browsers.txt to track compatibility Apr 20, 2015
gulpfile.js Initial commit (gulp, bower and boilerplate) Apr 13, 2015
package.json Version 0.4.7 Nov 20, 2017
protractor.conf.js Initial commit (gulp, bower and boilerplate) Apr 13, 2015
screenshot.png More fixes in README and optimized screenshot.png Dec 17, 2015


Jangouts (for "Janus Hangouts") is a solution for videoconferencing based on WebRTC and the excellent Janus Gateway with a user interface loosely inspired by Google Hangouts. It aims to provide a completely self-hosted open source alternative to Google Hangouts and similar solutions. Currently Jangouts supports conferences with video, audio, screen sharing and textual chat organized into an unlimited amount of conference rooms with a configurable limit of participants per room.

Example screen of Jangouts 0.4.0


Jangouts is a JavaScript application running exclusively client-side (i.e. in the browser). The server simply needs to provide a bunch of static files through a web server.

Step 1. Janus Gateway

All the server-side WebRTC handling is performed by Janus Gateway, so the first requirement is a running janus server with support for data channels compiled in, with the videoroom plugin enabled and with a valid list of rooms in the janus.plugin.videoroom.cfg file. For most Linux distributions that translates into installing the janus or janus-gateway package. Make sure those packages include data channels support. Compiling Janus Gateway from the sources is, of course, also an option.

For (open)SUSE distributions, a proper package can be easily found at and installed using 1 Click Install.

For security reasons, the (open)SUSE package does not include the SSL certificates shipped by default with Janus Gateway. To generate a self-signed certificate, use OpenSSL:

cd /usr/share/janus/certs
sudo openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 \
  -keyout mycert.key -out mycert.pem

In (open)SUSE, the gateway can be then started (after adjusting the list of rooms at /etc/janus/janus.plugin.videoroom.cfg if desired) with the command:

sudo systemctl start janus.service
sudo systemctl enable janus.service # to start it also after reboot

Step 2. Download and configure Jangouts

The easiest way to get Jangouts is to download the latest archive from the Jangouts releases page at Github. For deployment purposes, the only relevant directory in that archive is the one called dist, which contains the files to be served by the HTTP server to the participants' browsers. That includes the file called config.json that can be tweaked to point the participants to any Janus server, to enable extra debugging, etc. The file already contains sensible defaults that should work out of the box for most cases. It's fine to have some configuration parameters set to null in that file, Jangouts will try to guess the proper value during runtime.

If some Jangouts plugin is activated, it may need additional configuration in a separate file. See the corresponding section below.

Step 3. Serve the dist folder

Given than a Janus Gateway server is running and reachable and that config.json contains the proper values (usually just the default ones), all that needs to be done is to serve the content of the dist directory to the clients. Any web server, such as Apache, can be used for that purpose.

The simplest way (although not the cleanest) to do such thing in an (open)SUSE system would be:

  1. sudo zypper in apache2
  2. Copy the content of dist directly into /srv/www/htdocs/
  3. sudo systemctl start apache2.service

See the deployment instructions for more information about how to properly configure Apache.


Jangouts includes limited support for plugins in order to provide additional functionality. At the time of writing, the only available plugin provides integration with, a propietary third-party service to analyze WebRTC traffic and diagnose potential problems. In order to enable this plugin, write your credentials in a config.callstats.json file (following the syntax in config.callstats.json.sample) and set the following value in config.json.

enabledPlugins: ["callstats"]

If "callstats" is not listed in the list of enabled plugins, Jangouts will not include, download or execute any code coming from and will not connect to the servers in any other form.

A note about security and browsers

Browsers will refuse to allow screen sharing through WebRTC for connections not using SSL. In some cases, they will even refuse to send any WebRTC content at all, neither video or audio. Thus, to allow users of your Jangouts instance to use the screen sharing functionality (or, in some cases, to use Jangouts at all) you will have to provide HTTPS access to both the files and the Janus gateway, like shown in the deployment instructions.


If Jangouts does not work, please check the troubleshooting guide.

Developing Jangouts

In order to modify Jangouts, it's necessary to install some development tools. That setup is detailed in the development instructions.



This software is released under the terms of the MIT License. See the license file for more information.

Find us

Jangouts developers can be usually found at:

You can’t perform that action at this time.