Re: [Linphone-users] [Linphone-developers] Difference in date diplayed in call history

[julien.fb]

We are currently finalizing our latest version for desktop platforms. Please
do not hesitate to download the app from our daily builds here :
 Index of /snapshots (linphone.org).

 

Please let me know if this version has solved your issues.

 

Julien

 

De : Linphone-developers
 De la part de amurillo--- via Linphone-developers
Envoyé : mercredi 22 septembre 2021 15:45
À : linphone-users@nongnu.org; linphone-develop...@nongnu.org
Cc : amuri...@mercaprog.com
Objet : [Linphone-developers] Difference in date diplayed in call history

 

I’m using Linphone Desktop v4.2.5 on Windows 10, and I realized that in the
history call section the date of the calls is wrong, is reporting 1 day
before, in this example below the actual call date is Wednesday, September
22, you can see in this print screen that if you put the cursor above the
call time, appears the correct date:

 

 



 

Regards,

 

Andrés Murillo

IT Support

Cel: (506) 8824.7798

 

___
Linphone-users mailing list
Linphone-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/linphone-users

Re: [Linphone-users] Linphone does not ring anymore reliably

[ael via Linphone-users]

On Wed, Sep 22, 2021 at 10:55:59AM +0100, ael via Linphone-users wrote:
> On Sun, Sep 19, 2021 at 02:40:40PM +0100, ael via Linphone-users wrote:
> > On Sun, Sep 19, 2021 at 02:16:50PM +0200, Martin Glaser wrote:
> > > 
> > > Does 4.5.0 have a bug that prevents the reliable ringing? Are there known 
> > > problems with Apple's Notification system?
> > 
> > I too have had troubles with incoming calls not ringing. But with a
> > quite different environment (linux desktop) and version 
> > Desktop  - Qt5.15.2
> > Core 4.4.21
> > 
> > Using the sipgate registrar.
> 
> An update: the problem seems to be more serious than I had previously
> realised. I had arranged for a bank to call me back while using linphone
> to talk to them. When the call had finished, I was watching linphone
> awaiting the incoming call. Nothing. Linphone was displaying the sipgate 
> presence
> throughout.

I should have added that I am using the sipgate stun server. But I am
not behind my usual router, although I believe it has a sip gateway
although there is no explicit option to enable that.

I have added this note in the light of the other thread:
"hoping for help in protocol analyzation"

ael


___
Linphone-users mailing list
Linphone-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/linphone-users

Re: [Linphone-users] Linphone does not ring anymore reliably

[ael via Linphone-users]

On Sun, Sep 19, 2021 at 02:40:40PM +0100, ael via Linphone-users wrote:
> On Sun, Sep 19, 2021 at 02:16:50PM +0200, Martin Glaser wrote:
> > 
> > Does 4.5.0 have a bug that prevents the reliable ringing? Are there known 
> > problems with Apple's Notification system?
> 
> I too have had troubles with incoming calls not ringing. But with a
> quite different environment (linux desktop) and version 
> Desktop  - Qt5.15.2
> Core 4.4.21
> 
> Using the sipgate registrar.

An update: the problem seems to be more serious than I had previously
realised. I had arranged for a bank to call me back while using linphone
to talk to them. When the call had finished, I was watching linphone
awaiting the incoming call. Nothing. Linphone was displaying the sipgate 
presence
throughout.

When the bank contacted me on my mobile , they said that thay had tried
the linphone number 5 times, and in all cases the call switched to
voicemail. So it would seem that sipgate was flagging that I was not
connected/present/online.

There was a time when I knew a fair amount about the SIP protocol, but I
have forgotten most of it. But there is a time-out for registration and 
and an (optional) repeated handshake to maintain the presence IIRC.

It would seem that somehow linphone is failing to maintain that
presence/registration.

I don't have any logs to share. If I had expected the problem, I might
have enabled logging, but, of course, I was did not expect it.

I have been using sipgate without out problems for many years with
a variety of hard & soft 'phones. 

This is under debian testing. I have not logged a debian bug since the
maintainer is following this thread.

ael


___
Linphone-users mailing list
Linphone-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/linphone-users

Re: [Linphone-users] hoping for help in protocol analyzation

[boris]

Hej Dennis,

Am 2021-09-21 18:47, schrieb Dennis Filder:

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
https://ta6.short.gy/b8myTo

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.


Wow, prominent support - that makes me hope! Thank you in advance!


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://cx.dtst.de:5060], size: [423] 
bytes


What also seems strange to me is this:

Contact: 
@192.168.23.150;transport=udp>;expires=3600;+sip.instance=""


and this:

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


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
address.

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.


OK, I will try to draw conclusions from that. Do I understand correct, 
that I have to use either a STUN server or a local proxy to make 
LinPhone work fully?


As far as I could research until now, DT doesn't serve STUN.

And a local proxy would possibly prevent a second SIP service from being 
used on the LAN?


More facs from my local network:
a) The router is a full-configurable box based on APU Board with 
LEAF-software (http://leaf.zetam.org/), which is a purified small 
Linux.
b) There is a Panasonic KXsomething IP-Phone working all fine within the 
local network against the DT.

c) LinPhone works fine as well against an other SIP-Provider (TNG).
d) The disconnection after 15 minutes doesn't happen with Twinkle as 
softphone.



Good luck.


thanks and regards,

Boris

___
Linphone-users mailing list
Linphone-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/linphone-users