On Wed, 2009-07-08 at 08:32 -0400, Dan Mongrain wrote:
> RFC 3261 basically mentions that UAC can fail a transaction in the case
> of no response after 64*T1 (retransmitting every 2*T1). With the
> default T1 being 500ms, 32 seconds is a long time to wait especially
> when there are multiple p
ark R Lindsey
Sent: Wednesday, July 08, 2009 9:26 AM
To: Uttam Sarkar
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] SIP UDP timeout with multiple proxies
There are three issues here:
(a) Don't try to solve your application failover problems by monkeying
with SIP. Yo
oun...@lists.cs.columbia.edu] On Behalf Of
> Dan
> Mongrain
> Sent: Wednesday, July 08, 2009 8:32 AM
> To: sip-implementors@lists.cs.columbia.edu
> Subject: [Sip-implementors] SIP UDP timeout with multiple proxies
>
> Hi all,
>
> RFC 3261 basically mentions that UAC can
ntors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Dan
Mongrain
Sent: Wednesday, July 08, 2009 8:32 AM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] SIP UDP timeout with multiple proxies
Hi all,
RFC 3261 basically mention
Hi all,
RFC 3261 basically mentions that UAC can fail a transaction in the case
of no response after 64*T1 (retransmitting every 2*T1). With the
default T1 being 500ms, 32 seconds is a long time to wait especially
when there are multiple proxies available to process a request. Is
there a RF
