Re: [reSIProcate-users] Refresh registration as UAC
If the response does not contain an expires parameter on the contact
header, then it is violating RFC3261 section 10.3:
The registrar returns a 200 (OK) response. The response MUST
contain Contact header field values enumerating all current
bindings. Each Contact value MUST feature an "expires"
parameter indicating its expiration interval chosen by the
registrar. The response SHOULD include a Date header field.
As far as I know, there is no 18 minute fallback timer in resip, so
it's not really clear to me why that is happening at this point.
Scott
On Thu, Feb 11, 2010 at 2:29 PM, Richard Stellingwerff
<remenic@xxxxxxxxx> wrote:
> Thanks for replying Scott. Yes, 60 seconds is a bit low, I agree. The 200 OK
> does not include any expires value. I suppose that 5 minutes would be a more
> sane value, but even in such case the server doesn't reply with expires set
> to 300, and reSIProcate will refresh the session after 18 minutes... For me,
> that's too long.
> I suppose I could add a custom timer that calls
> ClientRegistation::requestRetry(300) after 300 seconds, but it sounds like a
> hack, rather than a real solution. Or is it?
> - Richard.
>
> 2010/2/11 Scott Godin <sgodin@xxxxxxxxxxxxxxx>
>>
>> Hi Richard,
>>
>> When you send the REGISTER you are requesting an expires time. It
>> doesn't mean that the server will honor it. In fact 60 seconds is so
>> low, I would not be surprised to learn that the registrar you are
>> using thinks the same and is returning another (higher) value to you
>> in the 200 response to the registration. Check the 200 response and
>> see what Expires value the registrar has specified.
>>
>> Scott
>>
>> On Thu, Feb 11, 2010 at 12:09 PM, Richard Stellingwerff
>> <remenic@xxxxxxxxx> wrote:
>> > Hi,
>> > I have a question concerning refreshing registrations as a UAC with
>> > reSIProcate. I have set the default registration timeout to 60 seconds,
>> > and
>> > the outgoing REGISTER message also has this value in the "expires"
>> > header.
>> > However, reSIProcate doesn't re-REGISTER when the expires time is
>> > reached. I
>> > decided to wait a bit longer, and after 1080 seconds I finally saw a new
>> > REGISTER being sent by reSIProcate. I don't understand why.. Am I doing
>> > something wrong?
>> > My goal is to detect when the connection to the SIP server is lost. It
>> > seems
>> > to detect stale calls fine (managed to get them to timeout after 65
>> > seconds
>> > of inactivity) but the registration won't timeout in a reasonable time.
>> > Any help is much appreciated.
>> > - Richard.
>> >
>> > _______________________________________________
>> > resiprocate-users mailing list
>> > resiprocate-users@xxxxxxxxxxxxxxx
>> > List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>> >
>
>