Jami quits with error "no internet connection"

icandothat · May 10, 2025, 8:29pm

I installed Jami yesterday, tested it with friends, and was VERY HAPPY to find something to replace skype for our team calls. I use skype for phone calls/team calls all day long. I saw that Jami would interface with VOIP.MS so I bought time on voip.ms, and started the configuration in Jami so could call out and it died. Now I can’t start Jami. I uninstalled it, installed the beta version, uninstalled that, deleted what I could find of registry entries, restarted the computer, uninstalled and re-installed, shut off the firewall(windows 10), did a windows update, etc. NOTHING, I can’t even get Jami to start.

icandothat · May 10, 2025, 8:49pm

This is the error I see before it dies.

ovari · May 11, 2025, 5:21am

Are there logs?

If there is an error shown in the logs, can you please create an issue on GitLab?

Thank you

icandothat · May 11, 2025, 8:08pm

I don’t know where there error logs are. Can someone point me in the right direction?

mmms · May 11, 2025, 8:35pm

In order to get the logs, you can start jami with the -d option. The documentation is here:

Here is an outline of the procedure:

First, you need to start a terminal or command prompt (cmd.exe on Windows), then you go to the Jami install directory, generally C:\Program Files\Savoir-Faire Linux\Jami

In that case, you need to type the following command in your terminal :
cd C:\Program Files\Savoir-Faire Linux\Jami

Then, you type Jami.exe -d -f %localappdata%\jami\jami.log on the command prompt and you will get all the logs in colors (quite overwhelming…) displayed in the terminal.

With the previous syntax, the complete logs will also be written in the jami.log file. To get that file, you simply need to type %localappdata%\jami\jami.log in your Windows file browser.

When I messed with Jami to add a voip.ms account, I had a similar problem where the program would fail to initialize properly. What I did is install an older version of Jami (e.g. 2024-12-19 here Index of /windows/archive), reinitialized the settings (in my case I had wrongly enabled SDES and TLS encyption in the Advanced settings, so I disabled these options). Eventually, I was able to upgrade to the latest Jami version again.

icandothat · May 12, 2025, 6:34pm

Awesome, thank you. Here’s my log with personal and account information redacted

[1747071234.784|7036|sipaccount.cpp [1747071234.786|7036|sipaccount.cpp [1747071234.786|7036] Unregistered [1747071234.794|7036|sipaccount.cpp [1747071234.794|7036|sipvoiplink.cpp [1747071234.796|7036|sipaccount.cpp [1747071234.796|7036|sipaccount.cpp [1747071234.796|7036|sipaccount.cpp [1747071234.796|7036|siptransport.cpp [1747071234.796|7036|siptransport.cpp [1747071234.796|7036|siptransport.cpp [1747071234.796|7036|sipaccount.cpp [1747071234.796|7036|sipaccount.cpp [1747071234.804|7036|sipaccount.cpp [1747071234.804|7036|sipaccount.cpp [1747071234.804|7036|jamiaccount.cpp [1747071234.804|7036|jamiaccount.cpp [1747071234.814|7036|jamiaccount.cpp [1747071234.814|7036] Desired [1747071234.816|7036] Request [1747071234.816|7036|jamiaccount.cpp [1747071234.816|7036|jamiaccount.cpp [1747071234.816|7036] Mapping Daemon is running
[1747071234.816|4312|jamiaccount.cpp [1747071234.847|4312|jamiaccount.cpp [1747071235.110|10400|jamiaccount.cpp [1747071235.260|7036|jamiaccount.cpp [1747071235.260|7036|jamiaccount.cpp [1747071235.260|7036|jamiaccount.cpp [1747071235.950|10400|jamiaccount.cpp [1747071235.950|10400|jamiaccount.cpp [1747071235.950|10400] [Account [1747071235.950|10400] [Account [1747071235.950|10400] Store [1747071235.950|10400] Setting [1747071235.950|7036|manager.cpp [1747071235.111|7036|manager.cpp :838 ] pjsip_regc_init failed with error 171039: Invalid URI (PJSIP_EINVALIDURI)
:741 ] VoipLinkException occurred: Unable to initialize account registration structure
mapping JAMI-UDP:5060
:635 ] UPnP: UPNP request failed, try to register SIP account anyway
:1511] Attempt to resolve ‘losangeles.voip.ms’ (port: 0)
:694 ] TLS is enabled for account REDACTED
:1093] Using 0 ciphers
:725 ] Creating transport
:100 ] ~SipTransport@0x1753f2b2f20 tr=0x1753f7a3578 rc=1
:367 ] Get new TLS transport to 208.100.60.35:5061
:79 ] SipTransport@0x1753f2b2a70 tr=0x1753f7a3578 rc=2
:370 ] Set new transport [0x1753f2b2a70]
:812 ] [Account REDACTED] Using contact header <sips:461907_REDACTED @192.168.0.111:60307;transport=tls> in registration
:838 ] pjsip_regc_init failed with error 171039: Invalid URI (PJSIP_EINVALIDURI)
:741 ] VoipLinkException occurred: Unable to initialize account registration structure
:1676] [Account REDACTED] Starting accountΓÇª
:2478] [Account REDACTED] ConnectingΓÇª
:1582] [Account REDACTED] UPnP: attempting to map ports
port is not set, will provide the first available port for [UDP]
for mapping JAMI-UDP:21174 failed, no IGD available
:1602] [Account REDACTED] DHT UPnP mapping changed to JAMI-UDP:21174 (state=FAILED, auto-update=YES)
:1643] [Account REDACTED] Mapping request is in FAILED state: starting the DHT anyway
JAMI-UDP:21174 will be requested when an IGD becomes available
:1879] [Account REDACTED] Starting accountΓÇª
:1703] [Account REDACTED] Bootstrap node: bootstrap.jami.net
:1979] [Account REDACTED] DHT status: IPv4 connecting; IPv6 disconnected
:1722] [Account REDACTED] Track presence for 100c832866670733330eebb74b570931a0d0b0e6
:1722] [Account REDACTED] Track presence for 4680204a2728a274a03af11d7674c5098b40e68f
:1722] [Account REDACTED] Track presence for b0740f8fa64f02fff18d6227a3f600d1af6e55c0
:1979] [Account REDACTED] DHT status: IPv4 connected; IPv6 disconnected
:2473] [Account REDACTED] Connected
REDACTED] Refresh cache for TURN server resolution
REDACTED] Cache refreshed for TURN resolution
DHT public IPv4 address: 68.6.173.26
the known public address to 68.6.173.26
:2651] Set accounts order: REDACTED/REDACTED/
:1748] Saving configuration to ‘C:\Users\REDACTED’