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. Regards Ranjit -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Iñaki Baz Castillo Sent: Monday, February 09, 2009 5:44 PM Cc: [email protected] Subject: Re: [Sip-implementors] "Reason-Header" inCANCELthroughvariousproxies 2009/2/9 Attila Sipos <[email protected]>: >>>Yes, in fact I hope you are right :) > > I do too!! > > I worry that one of the SIP heavyweights is going to correct me ( it's > happened before!! ) > > I'm sure they will add something to clarify! Let's wait for them :) -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
