Related
Install the gateway package. For general gateway server on Ubuntu, do as following: tar xf CS_WebRTC_Gateway_SIP.tgz cd Release-/ For GPU-accelerated gateway server on CentOS, do as following: tar xf CS_WebRTC_Gateway_SIP.hw.tgz cd Release-/ Launch the gateway server.
Categories
- HOME
pivot-table
symlink
rx-java2
jspdf
magento-1.9
tomcat7
field
aws-athena
adal
nivo-slider
atmega
django-filters
flurry
clickonce
docker-swarm
wixcode
jitsi
objectmapper
pdb
export-to-excel
scrapy-splash
bootstrapping
mutt
olingo
uitextfielddelegate
actionmailer
tcp-ip
ruta
lora
binary-search
appdomain
pymol
fusionreactor
dropzone
gnucash
google-api-java-client
hyperparameters
cordova-sqlite-storage
jenkins-shared-libraries
string-substitution
qcheckbox
geogebra
asp.net-core-1.0
uibarbuttonitem
settimeout
text-alignment
.net-4.5
mongoose-web-server
spark-view-engine
kakoune
oci8
hpoo
coroutine
ansible-vault
particles.js
advertising
bisonc++
wxhaskell
qtconsole
ztree
working-set
document-ready
transport
webobjects
php-ci
headset
l20n
famo.us
visio-vba
ccmenuitem
apple-maps
mydbr
sandbox-solution
virtual-earth
qsqltablemodel
mcafee
gpl
radscheduler
katta
tmx
gnu-toolchain
murmurhash
jdoql
grid-system
Resources
This document describes the required steps for a quick Jitsi Meet installation on a Debian based GNU/Linux system. Debian 8 (Jessie) or later, and Ubuntu 14.04 or later are supported out-of-the-box.
Debian Wheezy and other older systems may require additional things to be done. Specifically for Wheezy, libc needs to be updated.
Also note that a recent default Ubuntu installation has only the
main
repository enabled, and Jitsi Meet needs packages from universe
. Check your /etc/apt/sources.list
file, and if universe
is not present refer to Ubuntu's documentation on how to enable it. (Usually it amounts to copying the main
lines and changing to universe
.)N.B.:
a.) All commands are supposed to be run by root. If you are logged in as a regular user with sudo rights, please prepend sudo to each of the commands.
b.) You only need to do this if you want to host your own Jitsi server. If you just want to have a video conference with someone, use https://meet.jit.si instead.
Basic Jitsi Meet install
Add the repository
Update the package lists
(If you get an error:E: The method driver /usr/lib/apt/methods/https could not be found.run:
)
Install Jitsi Meet
Note : Something to consider before installation is how you're planning to serve Jitsi Meet. The installer will check if Nginx or Apache is present (with this order) and configure a virtualhost within the web server it finds to serve Jitsi Meet. If none of the above is found it then configures itself to be served via jetty. So if for example you are planning on deploying Jitsi Meet with a web server, you have to make sure to install the server before installing jitsi-meet.
During the installation, you will be asked to enter the hostname of the Jitsi Meet instance. If you have a FQDN hostname for the instance already set up in DNS, enter it there. If you don't have a resolvable hostname, you can enter the IP address of the machine (if it is static or doesn't change).
This hostname (or IP address) will be used for virtualhost configuration inside the Jitsi Meet and also, you and your correspondents will be using it to access the web conferences.
Generate a Let's Encrypt certificate
Simply run the following in your shell
Advanced configuration
If installation is on a machine behind NAT further configuration of jitsi-videobridge is needed in order for it to be accessible.Provided that all required ports are routed (forwarded) to the machine that it runs on. By default these ports are (TCP/443 or TCP/4443 and UDP 10000).The following extra lines need to be added the file
/etc/jitsi/videobridge/sip-communicator.properties
:See the documenation of ice4jfor details.
Default deployments on systems using systemd will have low default values for maximum processes and open files. If the used bridge will expect higher number of participants the default values need to be adjusted (the default values are good for less than 100 participants).To update the values edit
/etc/systemd/system.conf
and make sure you have the following values:![Install jitsi meet ubuntu studio 2017 Install jitsi meet ubuntu studio 2017](/uploads/1/2/5/8/125853287/632229569.png)
To load the values and check them look here for details.
By default, anyone who has access to your jitsi instance will be able to start a conferencee: if your server is open to the world, anyone can have a chat with anyone else. If you want to limit the ability to start a conference to registered users, set up a 'secure domain'. Follow the instructions at https://github.com/jitsi/jicofo#secure-domain.
Open a conference
Launch a web browser (Chrome, Chromium or latest Opera) and enter in the URL bar the hostname (or IP address) you used in the previous step.
Confirm that you trust the self-signed certificate of the newly installed Jitsi Meet.
Enjoy!
Adding sip-gateway to Jitsi Meet
Install Jigasi
or
During the installation, you will be asked to enter your SIP account and password. This account will be used to invite the other SIP participants.
Reload Jitsi Meet
Launch again a browser with the Jitsi Meet URL and you'll see a telephone icon on the right end of the toolbar. Use it to invite SIP accounts to join the current conference.
Enjoy!
Uninstall
Sometimes the following packages will fail to uninstall properly:
- jigasi
- jitsi-videobridge
When this happens, just run the uninstall command a second time and it should be ok.
The reason for failure is that sometimes, the uninstall script is faster than the process that stops the daemons. The second run of the uninstall command fixes this, as by then the jigasi or jvb daemons are already stopped.
Systemd details
To reload the systemd changes on a running system execute
systemctl daemon-reload
and service jitsi-videobridge restart
.To check the tasks part execute service jitsi-videobridge status
and you should see Tasks: XX (limit: 65000)
.To check the files and process part execute cat /proc/`cat /var/run/jitsi-videobridge.pid`/limits
and you should see: