1. re-transmission of re-INVITE TA SIP server | re-INVITE ---------------->| branch=A | re-INVITE ---------------->| branch=A | re-INVITE ---------------->| branch=A | re-INVITE ---------------->| branch=A | re-INVITE ---------------->| branch=A
2. re-transmission of REGISTER TA SIP server | REGISTER -------------->| branch=B | REGISTER -------------->| branch=B | REGISTER -------------->| branch=B | REGISTER -------------->| branch=B According RFC 3261 8.1.1.7 and 17.2.3 8.1.1.7 Via The branch parameter value MUST be unique across space and time for allrequests sent by the UA. The exceptions to this rule are CANCEL and ACK for non-2xx responses. As discussed below, a CANCEL request will have the same value of the branch parameter as the request it Section 17.1.1.3, an ACK for a non-2xx response will also have the same branch ID as the INVITE whose response it acknowledges 17.2.3 Matching Requests to Server Transactions 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. the matching rule does not include the comparison of branch parameter in server side. Should the branch parameter be the same when retransmitting? ----------------------------------------------------------------- 每天都 Yahoo!奇摩 海的顏色、風的氣息、愛你的溫度，盡在信紙底圖 http://tw.promo.yahoo.com/mail_premium/stationery.html _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
