[Home]

Summary:ASTERISK-15677: Attended transfer is broken on 1.6.2.4
Reporter:viniciusfontes (viniciusfontes)Labels:
Date Opened:2010-02-23 09:38:50.000-0600Date Closed:2010-03-03 12:10:53.000-0600
Priority:MajorRegression?Yes
Status:Closed/CompleteComponents:General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
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.
Comments:By: Pavel Litvinenko (pavell) 2010-02-25 04:54:27.000-0600

1.6.2 - works
1.6.2.2, 1.6.2.4 does not
By: Leif Madsen (lmadsen) 2010-02-25 13:16:25.000-0600

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.
By: viniciusfontes (viniciusfontes) 2010-02-25 18:35:58.000-0600

1.6.2.5 was released today. So the fix for this should be expected on 1.6.2.6?
By: Leif Madsen (lmadsen) 2010-03-03 12:10:26.000-0600

Assuming Asterisk 1.6.2.6 is not a security release, then yes it will be in 1.6.2.6.
By: Leif Madsen (lmadsen) 2010-03-03 12:10:53.000-0600

Fixed in the next non-security release version. 1.6.2.5 is a security release per the release announcement.