Hi,

Can someone help me with any RFC reference on how a server or a call
statefull Proxy should handle a SIP BYE which is using a wrong (duplicate)
branch parameter ?

Scenario:

1. A call is going on between two UAs through a call stateful proxy:



    UAC A ----> Proxy P1 -----> UAS B



2. UAC A sends SIP UPDATE. This SIP UPDATE is completed with 200 OK.

3. UAC A sends SIP BYE. The SIP BYE contains the same branch header as the
SIP UPDATE. Even the request-uri, to-tag, from-tag, call ID in SIP BYE are
same as SIP UPDATE. Only the CSeq header in SIP BYE is different than SIP
UPDATE.


My doubt is, should the call statefull proxy handle this BYE as normal
handling or reject the BYE or ignore the BYE.


RFC 3261 Section 17.2.3: Matching Requests to Server Transactions
For all other request methods, a request is matched to a transaction
if the Request-URI, To tag, From tag, Call-ID, CSeq (including the
method), and top Via header field match those of the request that
created the transaction.

So from the above, it seems that the BYE transaction does not match with
the UPDATE transaction and hence the proxy should handle this BYE as normal
processing. Please let me know my understanding is correct.



Thanks,
-- Prashanti
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to