# Linphone sip doesn't work with jami?

**URL:** <https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716>\
**Category:** Uncategorized\
**Created:** [July 4, 2026, 7:32pm UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716 "2026-07-04T19:32:12Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![eugenialoli](https://forum.jami.net/user_avatar/forum.jami.net/eugenialoli/32/1569_2.png) [@eugenialoli](https://forum.jami.net/u/eugenialoli)\
**Post date:** [July 4, 2026, 7:32pm UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/1 "2026-07-04T19:32:12Z")

</div>

I’m trying to connect to linphone via jami (Linux Mint). I added my username (my plain username without anything additionally) and password correctly, and I use this for server and proxy: sip:sip.linphone.org;transport=tls

TLS stuff are ON in the settings.

And yet, jami can never make a call out to anything (not even to 4443), and it always says “missed outgoing call”.

Any clues as to what is going on?

---

<div class="post-metadata">

**Author:** ![eugenialoli](https://forum.jami.net/user_avatar/forum.jami.net/eugenialoli/32/1569_2.png) [@eugenialoli](https://forum.jami.net/u/eugenialoli)\
**Post date:** [July 6, 2026, 9:16am UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/2 "2026-07-06T09:16:34Z")

</div>

Anyone please? Linphone is the most used service by Linux users, since they’re open source friendly. Since Jami claims that it can do SIP, Linphone is the one service that is expected to work. But it doesn’t? Can a developer test it and let us know what am I doing wrong here? Thx!

---

<div class="post-metadata">

**Author:** ![eugenialoli](https://forum.jami.net/user_avatar/forum.jami.net/eugenialoli/32/1569_2.png) [@eugenialoli](https://forum.jami.net/u/eugenialoli)\
**Post date:** [July 6, 2026, 1:13pm UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/3 "2026-07-06T13:13:37Z")

</div>

This is what I get from the command line when trying to place a call:

default [1783343506895][WRN][77ee52744480]: qrc:/settingsview/components/CustomizeProfilePage.qml:48:13: QML Connections: Detected function “onStopBooth” in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name.  
default [1783343506896][WRN][77ee52744480]: qrc:/settingsview/components/CustomizeProfilePage.qml:49: ReferenceError: settingsView is not defined  
libclient [1783343510777][DBG][77ee52744480]: Reading profile: “/home/eugenia/.local/share/jami/97d6bbe29e78563b/profile.vcf”  
libclient [1783343511227][DBG][77ee52744480]: Reading profile: “/home/eugenia/.local/share/jami/97d6bbe29e78563b/profile.vcf”  
libclient [1783343513239][DBG][77ee52744480]: Reading profile: “/home/eugenia/.local/share/jami/97d6bbe29e78563b/profile.vcf”  
libclient [1783343514402][DBG][77ee52744480]: Reading profile: “/home/eugenia/.local/share/jami/97d6bbe29e78563b/profile.vcf”  
libclient [1783343514823][DBG][77ee52744480]: Reading profile: “/home/eugenia/.local/share/jami/97d6bbe29e78563b/profile.vcf”  
libclient [1783343515234][DBG][77ee52744480]: Reading profile: “/home/eugenia/.local/share/jami/97d6bbe29e78563b/profile.vcf”  
libclient [1783343520365][DBG][77ee52744480]: Reading profile: “/home/eugenia/.local/share/jami/97d6bbe29e78563b/profile.vcf”  
default [1783343550605][DBG][77ee52744480]: “slotCallStateChanged (call: 2437867135942352), from Searching to Finished”  
default [1783343550606][DBG][77ee52744480]: “slotCallStateChanged (call: 2437867135942352), from Finished to Finished”  
default [1783343550607][DBG][77ee52744480]: Invalid JSON: “”

---

<div class="post-metadata">

**Author:** ![jschwart](https://forum.jami.net/user_avatar/forum.jami.net/jschwart/32/1580_2.png) [@jschwart](https://forum.jami.net/u/jschwart)\
**Post date:** [July 19, 2026, 6:13pm UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/4 "2026-07-19T18:13:41Z")

</div>

I managed to log in with my Linphone account (green indicator), but I guess I never tried making any calls. (I know chatting/SIMPLE is not working.) Does it make any difference what kind of phone is on the other end and maybe disabling TLS?

I do use Jami from time to time with IPPI ([https://www.ippi.com/](https://www.ippi.com/)) and my company’s SIP server and call functionality works then.

Linphone is probably one of the most advanced SIP/SIMPLE clients along with their server implementing quite a lot of things that do not seem to be implemented elsewhere. It would be interesting if Jami would be able to enhance its SIP/SIMPLE support similarly. There are cases where I cannot get messages across using Jami (especially when one peer lacks IPv6 connectivity) and Linphone does work in those cases.

---

<div class="post-metadata">

**Author:** ![eugenialoli](https://forum.jami.net/user_avatar/forum.jami.net/eugenialoli/32/1569_2.png) [@eugenialoli](https://forum.jami.net/u/eugenialoli)\
**Post date:** [July 19, 2026, 6:42pm UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/5 "2026-07-19T18:42:11Z")

</div>

Thank you for the reply. I only get orange indicator for linphone, not green. Could you give me the format of your settings?

Try to call 4443 and see if it works.

---

<div class="post-metadata">

**Author:** ![eugenialoli](https://forum.jami.net/user_avatar/forum.jami.net/eugenialoli/32/1569_2.png) [@eugenialoli](https://forum.jami.net/u/eugenialoli)\
**Post date:** [July 19, 2026, 6:47pm UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/6 "2026-07-19T18:47:14Z")

</div>

Another account to try calling is their test call: [thetestcall@sip.linphone.org](mailto:thetestcall@sip.linphone.org)

---

<div class="post-metadata">

**Author:** ![jschwart](https://forum.jami.net/user_avatar/forum.jami.net/jschwart/32/1580_2.png) [@jschwart](https://forum.jami.net/u/jschwart)\
**Post date:** [July 21, 2026, 6:46am UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/7 "2026-07-21T06:46:03Z")

</div>

I cannot call `4443` but `thetestcall` does work for me. (In Linphone I also cannot call `4443`.)

Under manage account I have this:

 ![image](https://forum.jami.net/uploads/default/original/2X/c/cb898f492bc3af395c08cd3480162ffb57542501.png)

I have these advanced settings:

 ![image](https://forum.jami.net/uploads/default/original/2X/c/c2f081a4977056bd4ef16f80181806c445c679bb.png)

---

<div class="post-metadata">

**Author:** ![eugenialoli](https://forum.jami.net/user_avatar/forum.jami.net/eugenialoli/32/1569_2.png) [@eugenialoli](https://forum.jami.net/u/eugenialoli)\
**Post date:** [July 21, 2026, 7:26am UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/8 "2026-07-21T07:26:41Z")

</div>

Thank you for the reply! It doesn’t work here. It says that “outgoing call missed”, it doesn’t try to dial. Do you think it’s a router problem? However the Linphone app itself works fine.

---

<div class="post-metadata">

**Author:** ![jschwart](https://forum.jami.net/user_avatar/forum.jami.net/jschwart/32/1580_2.png) [@jschwart](https://forum.jami.net/u/jschwart)\
**Post date:** [July 21, 2026, 4:21pm UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/9 "2026-07-21T16:21:44Z")

</div>

That might be. Do you have both IPv4 and IPv6? (It probably goes over IPv6 on my end.) If you only have IPv4 connectivity, possibly TURN/STUN will help. Linphone likely uses one of these by default.

I noticed that UPnP is enabled on my end, but that is not something actually active on my router. (My router is a Turris Omnia and I never set up UPnP on it.)

---

<div class="post-metadata">

**Author:** ![eugenialoli](https://forum.jami.net/user_avatar/forum.jami.net/eugenialoli/32/1569_2.png) [@eugenialoli](https://forum.jami.net/u/eugenialoli)\
**Post date:** [July 21, 2026, 7:59pm UTC](https://forum.jami.net/t/linphone-sip-doesnt-work-with-jami/5716/10 "2026-07-21T19:59:34Z")

</div>

I’m able to call myself, and nothing else… ☹

Also, I created an account with gitlab in order to do the bug report, and it says that my account is blocked, and that an admin will need to authorize it. I mean, come on…
