[asterisk-bugs] [Asterisk 0016513]: [patch] Transferee can hear silence on attended transfer when tranferer hangs up (MOH stops to play)
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jan 25 18:16:30 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16513
======================================================================
Reported By: litnimax
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 16513
Category: PBX/General
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
Target Version: 1.4.30
Asterisk Version: 1.4.28
JIRA: SWP-624
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-12-24 14:16 CST
Last Modified: 2010-01-25 18:16 CST
======================================================================
Summary: [patch] Transferee can hear silence on attended
transfer when tranferer hangs up (MOH stops to play)
Description:
How to reproduce.
1. "A" calls "B".
2. "B" picks up and talks to "A".
3. "B" makes attended transfer to "C". "A" hears MOH.
4. "B" does not wait until "C" picks up and "B" hangs up. MOH is stopped
(!) and "A" starts to hear nothing, just silence (!).
5. When atxfernoanswertimeout expires call is returned to "B". "A" can
again hear ringing.
See the log - http://asteriskpbx.ru/pastebin/30
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0008413 [patch] Upgrade for atxfer behaviour
related to 0016584 Attended feature transfers are broken i...
======================================================================
----------------------------------------------------------------------
(0117162) tilghman (administrator) - 2010-01-25 18:16
https://issues.asterisk.org/view.php?id=16513#c117162
----------------------------------------------------------------------
corruptor: they may or may not be, but past experience has shown that if
we conmingle reports where it is not clearly the same problem (when the
circumstances are different or the backtrace is not functionally
identical), then a report remains open for an extended period of time
because not all of the reporters with different problems can be easily
addressed with the same solution. On the other hand, it is extremely easy
to close 2 issues with the same commit, if they do turn out to be identical
in cause. Therefore, I repeat my request to open a separate issue for that
separate circumstance.
Issue History
Date Modified Username Field Change
======================================================================
2010-01-25 18:16 tilghman Note Added: 0117162
======================================================================
More information about the asterisk-bugs
mailing list