Prashanti Das <prashanti...@gmail.com> writes: > 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 ?
The receiver is allowed a great deal of latitude because the request is profoundly invalid. E.g., since the branch parameter is required to be unique, the receiver is allowed to assume that the request of the request is determined by the branch parameter. > 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. If the receiver detects that the branch parameter is a duplicate, the best choice is probably to reject it with a 400 response. That has the advantage that it notifies the sender of its incorrect behavior, which increases the chance that the administrator of the sender will correct its behavior. 21.4.1 400 Bad Request The request could not be understood due to malformed syntax. The Reason-Phrase SHOULD identify the syntax problem in more detail, for example, "Missing Call-ID header field". Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
