2009/2/9 Avasarala Ranjit-A20990 <[email protected]>: > Section 2 of RFC 3326 says > > Proxies generating a CANCEL request upon reception of a CANCEL from > the previous hop that contains a Reason header field SHOULD copy it > into the new CANCEL request. > > In normal SIP operation, a SIP status code in a response provides the > client with information about the request that triggered the > response, the session parameters, or the user. For example, a 405 > (Method not allowed) response indicates that the request contained an > unsupported method. A 488 (Not Acceptable Here) indicates that the > session parameters are unacceptable and a 486 (Busy Here) provides > information about the status of the user. > > So this means that Proxies SHOULD forward the CANCEL request that contains > Reason header.
Great! Thanks for pointing it out. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
