Should UPnP/TURN be good enough for my Jami Usage?

Hi all. We have been using Jami for over a year, without any kind of central JAMS or SIP server. I just set up endpoints on PCs on our network, where all endpoints are connected by VPN. We use Ubuntu 22.04 PCs for all Jami endpoints (disabling Wayland to stick with X11 for now). We only do audio with the Speex codecs. I enable UPnP and TURN and leave all settings as default (turn.jami.net, ring_device.key/crt, OpenDHT disabled I think). We use Jami because it can keep bandwidth on our over-the-air cellular or satellite network low (below 100 kbps bandwidth for a 2-way voice call). Two features that I would like to get working but have not been able to yet are call recording (I always end up with very small recorded files that just have some header info and no recorded voice data) and conferencing (I would need to get swarm working to do this??).

The call quality has been questioned by field personnel, in the areas of established call failures and not so much call establishment (though we have had issues with Jami not being able to be started and I have found that it’s already running and the existing process needs to be killed). They report that calls will fail and not be able to be re-established, or calls degrade over time. Some fielded endpoints probably do not have the latest release but my test endpoints now have 20240823.0 rev 317 installed. I am about to start some serious testing with the latest release.

I am reviewing the recent updates to Jami and it seems like it is more robust in recent releases, but I am wondering if using a server and the Enterprise model would add to robustness in my use case? Should I be able to assume that I can use the Community Edition of Jami for my use case?

Thanks

1 Like

my test endpoints now have 20240823.0 rev 317 installed

Suggest updating your all your clients, including your test endpoints, to Nightly 20241013. This release includes the conversation: fix swarm synchronization bug patch.

For better connectivity, all clients should have the ConnectionManager: retry pending connections on error patch. For more information, please see the developer note at High CPU usage and high data usage.

Please visit the changelog for more information on releases for GNU/Linux.

conferencing (I would need to get swarm working to do this??)

You may like to cc yourself into Allow removing member and related issues which has removeParticipant() isn't implemented yet. to be updated on development of this conferencing feature.

Thanks for the recommendations @ovari. I am unsure of how to install a nightly build like 20241013. It looks from the changelog like there are some good fixes there. Are there instructions someplace for how I can get this installed? Thanks

  1. Visit Download Jami for GNU/Linux
  2. Under “Please select your platform:”, click Ubuntu
  3. Click on Terminal instructions button
  4. Under “Option 1: install Jami from official repository”, click Beta version
  5. Copy instructions into Terminal (Ctrl+Alt+T)

Thank you! I will try this on Monday.

Another option is:

  1. Download the jami-all_amd64.deb installation file for Ubuntu 22.04 from Index of /ring-manual/ubuntu_22.04
  2. Open Terminal (Ctrl+Alt+T) in directory where download is located
  3. In the Terminal, type sudo dpkg -i jami-all_amd64.deb
  4. Enter the password and press Enter

The installation file might be able to be run by clicking on it too.

Copying the file to the other devices will reduce data being downloaded from the developers’ servers.

Only have experience installing Jami with Linux Mint Cinnamon edition; hence, sorry in advance if any of the instructions are incorrect.

I’m looking to make sure to get the 20241013 version that you mentioned, but what I see available is a 20241011 (317) version that has a data of 2024-10-13. Is this the right one?

snap info jami

jami
snap-id:      v2dLJDv8AcX1mtod8h5bmJknlYiIKNTJ
tracking:     latest/stable
refresh-date: 58 days ago, at 09:15 EDT
channels:
  latest/stable:    20240823.0 2024-08-24 (317) 298MB -
  latest/candidate: ↑                                 
  latest/beta:      ↑                                 
  latest/edge:      20241011.0 2024-10-13 (318) 298MB -
installed:          20240823.0            (317) 298MB -

Suggest you install the latest version (Nightly 20241023) shown at:

The version released after 20241013 includes a fix for the snap version.

The current deb version now is 202410232131. Have no experience with the snap version; however, the deb version should also work on your Ubuntu systems.

If you do install the deb versions, it is suggested that you first backup your accounts. Uninstalling the snap version may also be beneficial.

Hi @ovari. I looked at the Changelog and tried to look elsewhere for where i could download the actual build for the daily builds. I’m sorry that I could not find the builds. I should not have to build this myself right?

https://dl.jami.net/ring-manual/ubuntu_22.04/jami-all_amd64.deb