> From: Jeroen van Bemmel > > My question is: how should this be handled? Should reception > of a BYE abort > retransmission of the 2xx, or should the dialog linger as > long as the INVITE > server transaction has not finished? RFC3261 recommends that the UAS > responds to any remaining requests with a 487 Request > terminated, but since > it has already responded with 2xx I don't think it should > change its mind > for that one
IMHO, it's sort of a philosophical point which is straightforward when looked at correctly: Once the BYE is received, the *dialog* is eradicated, as both sides are in agreement that it has ended. But the *transaction* for the INVITE lives on (so it can retransmit the 200, and be quenched by receiving the ACK). And the transaction for the BYE lives on (to retransmit the response to the BYE if the other end retransmits the BYE). There are a number of similar situations that have been discussed on these lists. This probably isn't exactly the letter of RFC 3261, but it is clearly what is intended. Dale _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
