[asterisk-bugs] [Asterisk 0017486]: [patch] response_refer() does not have a default case, so a 400 final response stalls in the Transfer() application

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Aug 12 14:07:36 CDT 2010


The following issue has been set as RELATED TO issue 0012713. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17486 
====================================================================== 
Reported By:                davidw
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   17486
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Target Version:             1.6.2.12
Asterisk Version:           SVN 
JIRA:                       SWP-1667 
Regression:                 No 
Reviewboard Link:           https://reviewboard.asterisk.org/r/837/ 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 269011 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-06-08 11:34 CDT
Last Modified:              2010-08-12 14:07 CDT
====================================================================== 
Summary:                    [patch] response_refer() does not have a default
case, so a 400 final response stalls in the Transfer() application
Description: 
For an outgoing refer request, generated by the Transfer() application,
chan_sip.c's response_refer routine only recognizes specific response
codes, which don't include "400 Bad Request", the generic 400 response
code.

As a result, if it gets an unrecognized final status, it does not wake up
the Transfer application to allow it to return a FAILURE response to the
dialplan.  

Cisco CCM 6 can generate this response to REFER, although not necessarily
to the REFERs generated by the standard Asterisk code.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012713 [patch] SIP Protocol Violation when REF...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-12 14:07 mnicholson     Relationship added       related to 0012713  
======================================================================




More information about the asterisk-bugs mailing list