As per section 17.2.3. rfc 3261.
The INVITE request matches a transaction if the Request-URI, To tag,
From tag, Call-ID, CSeq, and top Via header field match those of the
INVITE request which created the transaction. In this case, the
INVITE is a retransmission of the original one that created the
transaction.
as per the section: 28.1
The branch parameter of the Via header field value is now
mandatory for all elements to use. It now plays the role of a
unique transaction identifier. This avoids the complex and bug-
laden transaction identification rules from RFC 2543. A magic
cookie is used in the parameter value to determine if the previous
hop has made the parameter globally unique, and comparison falls
back to the old rules when it is not present. Thus,
interoperability is assured.
The branch ID must be unique to identify the unique transaction.
On Wed, Feb 8, 2017 at 9:00 AM, dheeraj kumar <[email protected]>
wrote:
> As per section 17.2.3. rfc 3261.
>
> The INVITE request matches a transaction if the Request-URI, To tag,
> From tag, Call-ID, CSeq, and top Via header field match those of the
> INVITE request which created the transaction. In this case, the
> INVITE is a retransmission of the original one that created the
> transaction.
>
> as per the section: 28.1
>
>
> The branch parameter of the Via header field value is now
> mandatory for all elements to use. It now plays the role of a
> unique transaction identifier. This avoids the complex and bug-
> laden transaction identification rules from RFC 2543. A magic
> cookie is used in the parameter value to determine if the previous
> hop has made the parameter globally unique, and comparison falls
> back to the old rules when it is not present. Thus,
> interoperability is assured.
>
>
>
> On Fri, Jan 27, 2017 at 4:34 PM, Rakesh <[email protected]> wrote:
>
>> Dear Expert,
>>
>> Can UE reuse the same Call-ID, From tag and CSeq number, as it had used
>> for another INVITE which got terminated by 408, or it should really update
>> the Call-ID and/or From tag, to send the new INVITE request?
>>
>>
>> Is there any RFC 3261 section mentioned for this?
>>
>> *Best Regards*
>>
>> *Rakesh Kumar Mohanty*
>> _______________________________________________
>> Sip-implementors mailing list
>> [email protected]
>> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>>
>
>
>
> --
> Thanks and Regards
>
> Dheeraj kumar
>
> 9999733671
>
--
Thanks and Regards
Dheeraj kumar
9999733671
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
