Bugs item #1750761, was opened at 2007-07-09 16:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1750761&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: modules Group: ver 1.2.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Schlatter (cschlatter) Assigned to: Nobody/Anonymous (nobody) Summary: 6xx response doesn't cancel forked calls Initial Comment: RFC 3261 defines that upon reception of a 6xx response, a proxy SHOULD cancel all forked dialogs and send back the 6xx as the final response to the upstream UA. --- rfc 3261, section 16.7 ------- Under the new rules, upon receiving a 6xx, a proxy will issue a CANCEL request, which will generally result in 487 responses from all outstanding client transactions, and then at that point the 6xx is forwarded upstream. ---------------------------------- Some call forking experiments have shown that openser 1.2 does not follow these rules, instead it seems to disregard any 6xx response and continue with normal processing of existing forked dialogs. E.g. if a call forks to five phones and one of them sends back a 603 Declined response, the other four phones continue to ring until fr_inv_timer fires and failure_route is called with a status of 408 Timeout. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1750761&group_id=139143 _______________________________________________ Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
