Hi Ivar, Thanks a lot for your quick response [ 200 OK :) ], i am now all set to expedite the product release, i was stuck because of that.
- Mahesh On Jan 24, 2008 3:00 PM, Ivar Lumi <[EMAIL PROTECTED]> wrote: > > Hi, > > And hee it is: > > /* RFC 3261 17.1.3 Matching Responses to Client Transactions. > 1. If the response has the same value of the branch > parameter in > the top Via header field as the branch parameter in > the top > Via header field of the request that created the > transaction. > > 2. If the method parameter in the CSeq header field > matches the > method of the request that created the transaction. > The > method is needed since a CANCEL request constitutes a > different transaction, but shares the same value of > the branch > parameter. > */ > > Mahesh Pidshetti wrote: > > Hi > > > > " Ensure that the IUT, on receipt of a Success (200 OK) response *that > does > > not match to an existing client transaction *with a single Via header, > does > > not forward the message No Fwd Success (not matching to existing client > > transaction with single Via) " > > > > Please explain me how to identify the client transaction in SIP > > Messages/Methods. Is it identified by Call-ID or brachid or something > else. > > > > Thank you. > > > > > > - > > > > Mahesh > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
