[prev in list] [next in list] [prev in thread] [next in thread]
List: sip-implementors
Subject: Re: [Sip-implementors] Query on UAC Non Invite trasaction retransmission
From: "A C Sathish-a22713" <sathishac () motorola ! com>
Date: 2007-07-19 13:20:34
Message-ID: ACCC36A6A87F6F4090F816DA8BE86653D88D53 () ZMY16EXM66 ! ds ! mot ! com
[Download RAW message or body]
Thanks for the clarification.
-Regards,
Sathish
-----Original Message-----
From: Robert Sparks [mailto:rjsparks@nostrum.com]
Sent: Wednesday, July 18, 2007 9:19 PM
To: A C Sathish-a22713
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] Query on UAC Non Invite trasaction
retransmission
The receipt of the 100 trying resets Timer E to T2 no matter where you
are in the progression of doubling previous values of Timer E.
It might help to read about how this harms non-invite transactions -
there is a normative update to 3261 that makes that 100 trying not legal
until timer E would have been set to T2 anyhow. See RFCs 4320 and 4321.
RjS
On Jul 18, 2007, at 9:20 AM, A C Sathish-a22713 wrote:
> All,
> I have a query in the below scenario, Considering UAC is
> configured with T1 =500ms and T2=4s.
> UAC sends BYE to SIP Server and SIP Server responds with 100
> Trying only.
> In this case when UAC is supposed to retransmit the BYE ?
>
> Is it at T1 or T2 interval ?
>
> Below two sections indicates different behaviour .can any one clarify
> ?
>
> As per RFC 3261
> 17.1.2.1 Says
> "If a provisional response is received, retransmissions
> continue for unreliable transports, but at an interval of T2 "
>
> 17.1.2.2 " If Timer E fires while in the "Proceeding" state, the
> request MUST be
> passed to the transport layer for retransmission, and Timer E MUST
> be
> reset with a value of T2
> seconds." { Timer
> E will be set to T1 }
>
>
> Regards,
> -Sathish
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic