Jami crashes on incoming call

Generic topics
1

Using jami latest version (nightly repository) on Xubuntu 24.04. In “about jami” it says "astarte
version 202408241534. I am able to call out successfully with jami, but jami crashes with incoming call (it closes). In “account”, “advanced settings” I have tried various setting changes, but no joy. I have also tried enabling unpplay in my router, but that didn’t work. I am not quite sure if the logs show it, but here they are:

[1726520648.574|9130|manager.cpp :969 ] ############## START MONITORING ##############
[1726520648.574|9130|manager.cpp :970 ] Using PJSIP version 2.13.1 for x86_64-pc-linux-gnu
[1726520648.574|9130|manager.cpp :971 ] Using GnuTLS version 3.8.3
[1726520648.574|9130|manager.cpp :972 ] Using OpenDHT version 3.2.0
[1726520648.574|9130|manager.cpp :979 ] Opened files: 97
[1726520648.574|9130|manager.cpp :988 ] ############## END MONITORING ##############
[1726520650.886|9140] NAT-PMP: Trying to initialize IGD
[1726520650.886|9140] NAT-PMP: Initialized on gateway 10.0.0.1
[1726520650.892|9140] NAT-PMP: Read response on IGD 10.0.0.1 failed - NOGATEWAYSUPPORT
[1726520650.892|9140] NAT-PMP: Start search for IGDs. Attempt 3
[1726520680.892|9140] NAT-PMP: Trying to initialize IGD
[1726520680.892|9140] NAT-PMP: Initialized on gateway 10.0.0.1
[1726520680.895|9140] NAT-PMP: Read response on IGD 10.0.0.1 failed - NOGATEWAYSUPPORT
[1726520680.895|9140] NAT-PMP: Setup failed after 3 trials. NAT-PMP will be disabled!

2

Could you check journalctl and coredumpctl?

3

Where are they located, and what do I check for, and how do I post them here?

4

Run journalctl --since=<date> and search jami (type /jami and press enter).

5

Here is journalctl: (there was no coredump, and jami crashed a few seconds after 12:16:00)

~$ journalctl --since=12:16
Sep 17 12:16:15 marsdenf-Desktop jami[45168]: PUPnP: Already have a valid IGD. >
Sep 17 12:16:15 marsdenf-Desktop jami[45168]: NAT-PMP: Trying to initialize IGD
Sep 17 12:16:15 marsdenf-Desktop jami[45168]: NAT-PMP: Initialized on gateway 1>
Sep 17 12:16:15 marsdenf-Desktop jami[45168]: NAT-PMP: Read response on IGD 10.>
Sep 17 12:16:15 marsdenf-Desktop jami[45168]: NAT-PMP: Start search for IGDs. A>
Sep 17 12:16:28 marsdenf-Desktop jami[45168]: username = 218479_Desktop, server>
Sep 17 12:16:28 marsdenf-Desktop jami[45168]: Matching account id in request is>
Sep 17 12:16:28 marsdenf-Desktop jami[45168]: Received a SIP INVITE request
Sep 17 12:16:28 marsdenf-Desktop jami[45168]: Message headers:
Via: SIP/2.0/TLS 208.100.60.60:50>
Max-Forwards: 70
From: “Paco CALGARY AB”
To: <sips: 218479_Desktop @50.66.18>
Contact: <sip: 5878905216 @208.100.>
Call-ID: 7cd72bbf5823e9fa77bf01f8>
CSeq: 102 INVITE
User-Agent: voip .ms
Date: Tue, 17 Sep 2024 18:16:28 G>
Allow: INVITE, ACK, CANCEL, OPTIO>
Supported: replaces, timer
Remote-Party-ID: "Paco CALGARY AB>
Content-Type: application/sdp
Content-Length: 404
lines 1-23

(I have added some spaces here and there because I kept getting “sorry new users can only put two links in a post” messages)

6

Please use “ArrowDown” key and “ArrowUp” key to scroll…
:thinking:
I can’t reproduce the crash with a version released on June. Maybe I should upgrade… Or use the same SIP provider?

7

Okay, I found the problem. Jami didn’t like the custom ringtone I used (.wav file) and so I switched it to an .mp3 version of the same sound file, and now it works.