[reSIProcate] Timeouts?

[Scott Godin]

RFC3261 requires retransmission of un-responded to requests for 32
seconds at a declining rate.  You can find more info on this in the RFC.

Once the transaction times out.  There is a callback (ie.
onRequestRetry) to let the app decide if retrying is desired.  Returning
0 from this callback requests an immediate retry.

There is also a profile setting for registrations:  
// The time to retry registrations on error responses (if Retry-After
header is not present in error)
// Set to 0 to never retry on errors (falls back to onRequestRetry
mechanism)
virtual void setDefaultRegistrationRetryTime(int secs);

Scott

> -----Original Message-----
> From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-
> devel-bounces at list.sipfoundry.org] On Behalf Of
> Christian_Gavin at logitech.com
> Sent: Thursday, October 27, 2005 1:53 PM
> To: resiprocate-devel at list.sipfoundry.org
> Subject: [reSIProcate] Timeouts?
> 
> Hi,
> 
> How does one control in reSIProcate with DUM
> 
> 1) how many retries for a given message (REGISTER, INVITE, SUBSCRIBE,
> etc).
> 
> 2) the timeout after which retries are not sent anymore
> 
> Right now, REGISTERs seem to be sent forever if the server does not
> respond. Also, SUBSCRIBEs are sent continually if the other side
doesn't
> respond.
> 
> Thanks,
> Christian
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel