[Kamailio-Devel] [ openser-Feature Requests-2581449 ] Support for RFC 3326 (respect "Reason" header in CANCEL)

SourceForge.net noreply at sourceforge.net
Tue Feb 10 14:21:52 CET 2009


Feature Requests item #2581449, was opened at 2009-02-09 13:46
Message generated for change (Comment added) made by oej
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743023&aid=2581449&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: ver devel
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Iñaki Baz (ibc_sf)
Assigned to: Nobody/Anonymous (nobody)
Summary: Support for RFC 3326 (respect "Reason" header in CANCEL)

Initial Comment:
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 include the "Reason" header in its CANCEL if it receives a CANCEL containing it.

This would be very useful in big SIP environments involving various proxies.

Another different subject would be Kamailio adding by itself a "Reason" header to inform the cancelled branches about the reason of the cancellation (ie, "Call answered elsewhere"). But this is a different and independent wish/feature.


----------------------------------------------------------------------

Comment By: Olle E. Johansson (oej)
Date: 2009-02-10 14:21

Message:
Asterisk has support for this header from version 1.6.0.

----------------------------------------------------------------------

Comment By: Iñaki Baz (ibc_sf)
Date: 2009-02-09 17:52

Message:
I add a link to a thread in SIP-implementors maillist about this subject:
 
https://lists.cs.columbia.edu/pipermail/sip-implementors/2009-February/021634.html

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743023&aid=2581449&group_id=139143



More information about the Devel mailing list