Linphone doesn't work

Projet:Trisquel
Version:8.0
Composant:Programs
Catégorie:Demande d'aide
Priorité:normal
Attribué:Non assigné
Statut:active
Description

Hello, I've installed Linphone as a libre alternative to Skype. It's important for family relations. After starting Linphone, I have to enter my password once or twice. But I'm not able to make a call, receive a call or see the status of contacts. They also can't call me and don't see my status. I also can't make any test calls, e.g. name at domain or name at domain. In my router (AWN Fritz!Box), I've configured channel 5061 for UDP and I've set Linphone to UDP/5061 as well. Please find attached the content of my debug window. Thanks in advance for your help! Florian

Fichier attachéTaille
linphone-debug-window.txt40.6 Ko
mar, 01/14/2020 - 22:00

> I've configured channel 5061 for UDP and I've set Linphone to UDP/5061

In your attachment I see

```
error: eXosip_dnsutils_naptr_lookup: res_query failed ('sip.linphone.org NAPTR')
message: DNS resolution with sip.linphone.org:5060
message: getaddrinfo returned: 91.121.209.194 port 5060
message: Message sent: (to dest=91.121.209.194:5060)
```

Searching for that error, I found

https://lists.gnu.org/archive/html/linphone-users/2017-02/msg00008.html

in which the author of the message has also configured their Linphone to use a non-default port and ran into a similar error to yours. They say that it works the default port, 5060, so try that first. If Linphone works for you with the default port, then you likely have the same issue, in which case see if the settings posted in response to them help. If Linphone works with neither port, then the issue is something else and we'll keep looking.

I recommend making posts like this one on the forum instead of the issue tracker. Not many people check the issue tracker, so your post is more likely to be seen by someone who can help you if you go to the forum first. Once it has been determined that there is indeed a bug (as opposed to an incorrect configuration), and you know where the issue lies and what needs to be done, then it makes sense to go to the issue tracker.

jeu, 01/16/2020 - 16:13

Thank you very much! I tried again both with the standard port 5060 and port 5061. It didn't work. Now I'm going to transfer my support request to the forum. Thanks again.