Commands to Access and Use the Intulse Meetings Server

The Intulse Meetings project is built off the open source project Jitsi-Meet. Therefore, it is deployed on a Linux server and, when accessing it, you will need to use the command line to perform all of the actions and diagnostics required to manage the Intulse Meetings Project.

Logging into the Server

1. Open a command prompt
2. Use the following command to attempt a log in:
   1. ssh [email protected]
3. You will now be prompted for a password. Type in the password to access the server (you can get the password from Adam or Darren).

Get the Latest Intulse Meetings Changes

When you make changes to the Intulse Meetings project, you should be developing changes in their own feature branches and then create pull requests to merge those changes into the Intulse branch (which functions as master for this project). Once you have your local change pushed to the Intulse branch you should be able to log into the server (see the above instructions), open a command prompt, and us the following commands to pull the latest changes into production and deploy those changes to the server:

1. cd /home/intulseadmin/intulse-jitsi-meet
2. git pull
   1. NOTE: This will pop up a commit message screen; just click CTRL + X to save and exit
3. make
4. sudo ./deploy-local.sh

Important Folders

On the production server there are two important folders:

• /home/intulseadmin/intulse-jitsi-meet
• /usr/share/jitsi-meet

You can use the cd command to access either of these folders (for example, cd /usr/share/jitsi-meet).

Update Jitsi Components

You can update the Jitsi components on the server by running the following commands:

1. sudo apt-get update && sudo apt-get upgrade
   1. This gets the latest Jitsi components packages and upgrades them to use the latest ones available
2. service nginx restart && service jitsi-videobridge2 restart && service prosody restart && service jicofo restart
   1. This restarts all of the Jitsi services

Monitor Logs

There are three important logs on the Jitsi server that are important to monitor when there is some sort of issue.

Video Bridge

The video bridge code can be found in Jitsi's Github:

https://github.com/jitsi/jitsi-videobridge

The readme on that page describes the video bridge as:

Jitsi Videobridge is an XMPP server component that allows for multiuser video communication. Unlike the expensive dedicated hardware videobridges, Jitsi Videobridge does not mix the video channels into a composite video stream, but only relays the received video channels to all call participants. Therefore, while it does need to run on a server with good network bandwidth, CPU horsepower is not that critical for performance.

You can monitor the logs for the video bridge using the following command:

tail -F /var/log/jitsi/jvb.log

Jicofo

Jicofo stands for JItsi COnference FOcus. Essentially, this is the component that handles making sure each user's screen is properly focused on the appropriate candidate. You can find more details and the source code here:

https://github.com/jitsi/jicofo

You can monitor the jicofo logs using the following command:

tail -F /var/log/jitsi/jicofo.log

Prosody

Prosody is an XMPP server (if you don't know what XMPP is, feel free to read this: https://getstream.io/blog/xmpp-extensible-messaging-presence-protocol/). The Jitsi team explains the importance of this component here. In summary:

all components connect to it so they can communicate using xmpp protocol, this includes web, jicofo, jvb and the rest of the components. Jicofo is the first to enter a room and orcestrates the conference, sending invites, opening channels on the videobridge and such.

You can monitor the Prosody logs using the following command:

tail -F /var/log/prosody/prosody.log

NGINX

The NGINX website does a good job of explaining what this component does:

NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability.

You can monitor the NGINX logs using the following command:

tail -F /var/log/nginx/error.log