[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Linphone-developers] MESSAGE Channel [0x7d38856a00]: inactivity tim
From: |
Brian J. Murrell |
Subject: |
Re: [Linphone-developers] MESSAGE Channel [0x7d38856a00]: inactivity timeout reached |
Date: |
Tue, 16 Apr 2019 07:48:14 -0400 |
User-agent: |
Evolution 3.30.5 (3.30.5-1.fc29) |
On Tue, 2019-04-16 at 13:07 +0200, Marc Bohets wrote:
> The sip re-registration timer is imposed by the VoIP provider.
Yes, I understand that. I am the "VoIP provider". That is, I am
registering my linephone clients to my own PBX. So I control the re-
registration timer maximum.
> Initially, a sip client may send its preferred registration time to
> the sip
> server,
> but it is the sip server (= VoIP provider) that decides on the
> registration
> timing.
Yes, completely understood. My PBX allows an expiry of 48hrs:
SIP/2.0 200 OK
Via: SIP/2.0/UDP
[2001:1234:5678:abcd:fd9c:35ad:a810:fb17]:49017;rport=49017;received=2001:1234:5678:abcd:fd9c:35ad:a810:fb17;branch=z9hG4bK.Dl3boZnIx
Call-ID: xfsPYrbSC3
From: <sip:address@hidden>;tag=THAILF5nQ
To: <sip:address@hidden>;tag=z9hG4bK.Dl3boZnIx
CSeq: 184 REGISTER
Date: Mon, 15 Apr 2019 09:57:33 GMT
Contact:
<sip:address@hidden:1234:5678:abcd:fd9c:35ad:a810:fb17]:49017;transport=udp;app-id=755770037818;pn-type=firebase;pn-tok==[redacted];pn-silent=1>;expires=172799
Expires: 172800
Server: Asterisk PBX 13.25.0
Content-Length: 0
as you can see.
But this issue does not seem to be about the SIP "Expires" timeout.
Rather, it's about some kind of "transport inactivity" timeout which
defaults to 3600s:
https://github.com/BelledonneCommunications/belle-sip/blob/1d083c76be5b5959db2cc1f52a61836d8f43aa7f/src/sipstack.c#L137
and is settable to a different value here:
https://github.com/BelledonneCommunications/belle-sip/blob/1d083c76be5b5959db2cc1f52a61836d8f43aa7f/src/sipstack.c#L298-L300
But if this timer is going to force re-registration by the client,
surely the client -- I would presume through liblinphone -- needs to
set this timeout to be the same as the client-and-PBX agreed on Expires
timeout, at minimum, yes?
But being very new to this stack, it's quite likely there is something
I am missing.
Cheers,
b.
signature.asc
Description: This is a digitally signed message part