[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Linphone-users] hoping for help in protocol analyzation

From: Dennis Filder
Subject: [Linphone-users] hoping for help in protocol analyzation
Date: Tue, 21 Sep 2021 18:47:00 +0200

On Tue, Sep 21, 2021 at 04:16:39PM +0200, Boris wrote:

> The problems in short words:
> 1. An incoming call cannot be accepted: Pressing the green handset gives an
> 'unreachable' message to the caller.
> 2. An outgoing call works just fine but terminates reproduceable after 15
> minutes and some seconds.
> So I waited for an uptodate LinPhone on Debian Bullseye - and here it is:
> LinPhone is on Qt5.15.2 Core 4.4.21 in Debian 11 and I would be very glad to
> make it work!
> I made a logfile for the second issue but I am unable to analyze it due to
> volume an complexity. Is anybody about to help?
> Have a look at the log from
> In fact the SIP-provider is in my focus. He seems to use unusual settings
> for his service but doesn't give support for me as being an "exotic" user.
> So I hope it should be possible to find it out wit the log.

Debian maintainer here.  The error message is this:

> 2021-09-17 09:03:39:036 [linphone/belle-sip] MESSAGE Changing [server] 
> [INVITE] transaction [0x562792d3ab20], from state [ACCEPTED] to [TERMINATED]
> 2021-09-17 09:03:39:037 [linphone/belle-sip] MESSAGE Server INVITE 
> transaction [0x562792d3ab20] terminated
> 2021-09-17 09:03:39:037 [linphone/belle-sip] ERROR Dialog [0x562792cb0310] 
> was not ACK'd within T1*64 seconds, it is going to be terminated.
> 2021-09-17 09:03:39:037 [linphone/belle-sip] MESSAGE Dialog [0x562792cb0310]: 
> now updated by transaction [0x5627930a4f30].
> 2021-09-17 09:03:39:037 [linphone/belle-sip] MESSAGE Transaction 
> [0x562792d3ab20] deleted
> 2021-09-17 09:03:39:037 [linphone/belle-sip] MESSAGE Changing [client] [BYE] 
> transaction [0x5627930a4f30], from state [INIT] to [TRYING]
> 2021-09-17 09:03:39:037 [linphone/belle-sip] MESSAGE channel 
> [0x562790930250]: message sent to [UDP://], size: [423] bytes

What also seems strange to me is this:

> Contact: 
> <sip:<YOURPHONENUMBER>@;transport=udp>;expires=3600;+sip.instance="<urn:uuid:317ed210-8b23-0033-b9c2-cf1a4451f191>"

and this:

> 2021-09-17 08:26:25:478 [linphone/belle-sip] MESSAGE channel 
> [0x562790930250]: discovered public ip and port are []

As far as I can tell you're not using a local SIP proxy to connect to
DT's SIP gateway.  But you don't seem to have a STUN server set up
either.  Thus my guess is that Linphone has no way of knowing what it
has to fill in the messages as your public IP address (SIP needs these
addresses to be routable, so using a local IP address only works when
using a local SIP proxy), so it uses the one on your local network
card.  I suspect the confusion arising from that is never resolved and
it is large enough for Linphone to no longer be able to link incoming
messages to existing connections, thus timeout timers are not reset as
they should be leading to the connection termination.  This is
accompanied by this message:

> 2021-09-17 09:03:07:018 [linphone/liblinphone] MESSAGE Local stream 
> description has changed: NETWORK_CHANGED

This indicates that Linphone's idea of the network configuration has
changed, but apparently it does not change its idea of the public IP

You might have to enable STUN/TURN on your Internet router (assuming
its firmware supports that) and then configure Linphone accordingly.
Alternatively, use your router's SIP proxy as the next hop.

Good luck.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]