Re: [reSIProcate-users] Refresh registration as UAC
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/
>