From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= <[EMAIL PROTECTED]> - Proxy (stateful proxy) must reply with "200 cancelling" and send a CANCEL to every branches. [1] - In this "200 cancelling" sent to UAC the To_tag SHOULD be the same as in the response to the original request of the UAC. [2]
So, how can it be possible? which To_tag SHOULD contain the "200 cancelling"? "aaa" or "bbb"? they are various previous responses with To_tag !! It does not appear to me that there is a requirement that when a proxy sends a 200 response to a CANCEL that the to-tag of the response match any other response that has been generated. See RFC 3261 section 16.10. It is true that when a UAS generates a response to a CANCEL it "SHOULD" use the same to-tag as in the (future) 487 response to the request being canceled or in the (past) final response to that request. See RFC 3261 section 9.2. In fact, I've problem with Asterisk in mode "pedantic=yes" (matching To and From tags) when sending a CANCEL to an OpenSer that does parallel forking. Asterisk doesn't recognize the "200 canceling" because the To_tag is different of the previously received To_tag in 180 response, so Asterisk remains the channel open. Given that the requirement is at SHOULD level, and it appears to apply only to UASs, not proxies, it appears that Asterisk is behaving incorrectly. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
