[asterisk-bugs] [Asterisk 0016563]: r236981 Attended transfer fails to complete if A calls B, B uses Asterisk atxfer to C, and C picks up before B hangs up
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Feb 4 14:39:34 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16563
======================================================================
Reported By: aragon
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16563
Category: Channels/chan_features
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
Target Version: Potential Blocker
Asterisk Version: SVN
JIRA: SWP-679
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 236981
Request Review:
======================================================================
Date Submitted: 2010-01-07 08:17 CST
Last Modified: 2010-02-04 14:39 CST
======================================================================
Summary: r236981 Attended transfer fails to complete if A
calls B, B uses Asterisk atxfer to C, and C picks up before B hangs up
Description:
Attended transfer fails to complete if A calls B, B uses Asterisk atxfer to
C, and C picks up before B hangs up.
Screened calls with Asterisk DTMF atxfer are not possible in r236981
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0016584 Attended feature transfers are broken i...
related to 0016701 [regression] Attended transfer broken i...
======================================================================
----------------------------------------------------------------------
(0117742) lmadsen (administrator) - 2010-02-04 14:39
https://issues.asterisk.org/view.php?id=16563#c117742
----------------------------------------------------------------------
Please note that "trunk" is a specific thing, and referring to "1.4.29
trunk" or "1.4.30 trunk" is just wrong.
trunk: it's trunk, where new development happens
1.4, or 1.6.0: branch <-- branches come from the trunk, just like a tree
1.4.29, or 1.4.30: release <-- snapshot of a branch in time
Not sure exactly which commit *could* have fixed the transfer issue --
244151 could have fixed it.
'svn log | more' is useful for getting a log of changes.
Issue History
Date Modified Username Field Change
======================================================================
2010-02-04 14:39 lmadsen Note Added: 0117742
======================================================================
More information about the asterisk-bugs
mailing list