[asterisk-bugs] [Asterisk 0016886]: Attended transfer is broken on 1.6.2.4

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Feb 25 13:16:25 CST 2010


The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=16886 
====================================================================== 
Reported By:                viniciusfontes
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16886
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.4 
JIRA:                        
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-02-23 09:38 CST
Last Modified:              2010-02-25 13:16 CST
====================================================================== 
Summary:                    Attended transfer is broken on 1.6.2.4
Description: 
Attended transfer doesn't work on 1.6.2.4 when using the atxfer DTMF
sequence defined on features.conf.

Scenario:

A calls B
B answers and type the atxfer DTMF sequence followed by C's extension
number
C answers and hears the ringback tone instead of talking to B
B talks to A again when the timeout occurs.
====================================================================== 

---------------------------------------------------------------------- 
 (0118565) lmadsen (administrator) - 2010-02-25 13:16
 https://issues.asterisk.org/view.php?id=16886#c118565 
---------------------------------------------------------------------- 
This issue is already resolved in the release candidates for 1.6.2.3-rc2
(and others). 1.6.2.4 was a security release based on 1.6.2.2 as per the
release announcement.

This fix will be available in the next full release of Asterisk. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-25 13:16 lmadsen        Note Added: 0118565                          
2010-02-25 13:16 lmadsen        Status                   new => closed       
======================================================================




More information about the asterisk-bugs mailing list