[asterisk-bugs] [Asterisk 0012713]: [patch] SIP Protocol Violation when REFER rejected in sip_transfer (Cisco CCM, post answer), and Transfer application misclaims

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Aug 18 08:10:40 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=12713 
====================================================================== 
Reported By:                davidw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12713
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.20 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-05-23 12:59 CDT
Last Modified:              2010-08-18 08:10 CDT
====================================================================== 
Summary:                    [patch] SIP Protocol Violation when REFER rejected
in sip_transfer (Cisco CCM, post answer), and Transfer application misclaims 
Description: 
A call from Cisco CCM was answered and then transferred back to a different
extension on the Cisco.

Asterisk first reported a successful TRANSFERSTATUS, then tried to use a
REFER method.  This was rejected as unsupported.  Asterisk responded with
BYE, which the Cisco accepted.  However it continued to try to send REFERs,
which the Cisco, of course, rejected, because the session reference had
been deleted by the BYE!
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0010052 NOTIFY race condition when state change...
related to          0011848 Incorrect dialog matching and requests ...
related to          0017486 [patch] response_refer() does not have ...
====================================================================== 

---------------------------------------------------------------------- 
 (0126090) svnbot (reporter) - 2010-08-18 08:10
 https://issues.asterisk.org/view.php?id=12713#c126090 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 282639

U   branches/1.8/channels/chan_sip.c

------------------------------------------------------------------------
r282639 | mnicholson | 2010-08-18 08:10:37 -0500 (Wed, 18 Aug 2010) | 13
lines

Properly handle 200 and unknown responses conatined in NOTIFY requests
received in response to REFER requests.

This patch fixes the way asterisk handles NOTIFY requests received in
response to REFER requests.  These changes to NOTIFY handler were first
introduced in r217482.  This new change properly handles the 200 response
by queueing an AST_TRANSFER_SUCCESS control frame and also prevents that
control frame from being queued when provisional and unknown responses are
received.

(issue https://issues.asterisk.org/view.php?id=17486)
Reported by: davidw
Tested by: mnicholson

(issue https://issues.asterisk.org/view.php?id=12713)
Reported by: davidw

Review: https://reviewboard.asterisk.org/r/860/

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

http://svn.digium.com/view/asterisk?view=rev&revision=282639 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-18 08:10 svnbot         Checkin                                      
2010-08-18 08:10 svnbot         Note Added: 0126090                          
======================================================================




More information about the asterisk-bugs mailing list