[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Linphone-developers] MESSAGE Channel [0x7d38856a00]: inactivity tim
Brian J. Murrell
Re: [Linphone-developers] MESSAGE Channel [0x7d38856a00]: inactivity timeout reached
Tue, 16 Apr 2019 07:48:14 -0400
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
> but it is the sip server (= VoIP provider) that decides on the
Yes, completely understood. My PBX allows an expiry of 48hrs:
SIP/2.0 200 OK
CSeq: 184 REGISTER
Date: Mon, 15 Apr 2019 09:57:33 GMT
Server: Asterisk PBX 13.25.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:
and is settable to a different value here:
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.
Description: This is a digitally signed message part