Hi Johnny, ----- Original Message ----- > From: "Johnny Markiewicz" <joh...@sonicwebdev.com> > To: jami@gnu.org > Sent: Wednesday, August 2, 2023 9:27:54 AM > Subject: jami client
> Hi, > > I'm trying to build and run jami client from source on my machine. I have > configured asterisk server running on my machine but I am unable to > register SIP user from jami client. > In logs I found such message: > > NetworkManager client initialized, version: , daemon running: no , > networking enabled: no > no primary network connection detected, check network settings > > I think the problem here is that client can't see daemon and the whole > transport does not work. Could you explain how I should run jami-client to > use daemon running as separate process? Or running jami client should setup > daemon itself and I don't need to run it separately? Most Jami clients nowadays are built with the -DENABLE_LIBWRAP=ON build option which causes it to link to libjami directly (which is the core/daemon code), so a separate daemon (jamid) process is not needed. But if you built it yourself it may be built to use a daemon, in which case the daemon needs to run first yes. The binary is called 'jamid'. There's a Python script to easily build jami from source, you can e.g. ./build.py --install to build, then ./build.py --run to run it. The script builds jami with the -DENABLE_LIBWRAP=ON option by default. I hope that helps! Maxim
