Summary: | ASTERISK-15367: [patch] Transferee can hear silence on attended transfer when tranferer hangs up (MOH stops to play) | ||
Reporter: | Max Litnitskiy (litnimax) | Labels: | |
Date Opened: | 2009-12-24 14:16:00.000-0600 | Date Closed: | 2010-02-22 16:04:10.000-0600 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | PBX/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) atxfer_moh_16513.patch ( 1) transfer-log.txt | |
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 | ||
Comments: | By: David Woolley (davidw) 2010-01-05 06:26:42.000-0600 This is a features transfer not a SIP transfer, although it is on a SIP connection. Could you please upload the trace to the actual bug tracker as people might want to refer to this issues long after it is resolved and that is the only way of making sure that the trace can be found. By: Max Litnitskiy (litnimax) 2010-01-05 07:07:42.000-0600 Yes, it's a feature transfer. Where shall I put the trace? Right here as a note? By: David Woolley (davidw) 2010-01-05 07:10:15.000-0600 Use the Upload File section of this form. Do not tick the code or documentation option. By: Guillaume Knispel (gknispel_proformatique) 2010-01-05 09:22:35.000-0600 We recently had the same problem and wrote a little patch to workaround it. When applied, if you reproduce steps: 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. it results in that: a. if "C" is still ringing, "A" will still hear MOH until either "C" answers or hangs up (or the call is dropped, etc...). b. if "C" answers, "A" and "C" will be connected; c. or if "C" hangup (or the call is dropped, etc...), the transfer attempt terminates. By: Max Litnitskiy (litnimax) 2010-01-05 14:11:23.000-0600 But why it's not in trunk already!? By: Guillaume Knispel (gknispel_proformatique) 2010-01-06 03:55:19.000-0600 Because I don't have commit privileges? (and I'm not requiring some) By: Morten Tryfoss (mtryfoss) 2010-01-20 03:56:20.000-0600 There's a similar issue in 1.6.1.13. 1. A calls B 2. B picks up and talks to A 3. B does attended transfer to C 4. C picks up, but B still hears ringing 5. A and B are connected again (AT timeout exceeded on console) By: Tilghman Lesher (tilghman) 2010-01-22 13:49:38.000-0600 mtryfoss: I'd advise you to file a separate issue. That's a completely separate problem, as the code is radically different in 1.6.1. By: Andrey Solovyev (corruptor) 2010-01-25 03:10:52.000-0600 tilghman: There is the same issue (as mtryfoss describes) 0016584 for 1.6.0.21 and it is closed as dup to this one. Aren't all those transfer problems related? By: Tilghman Lesher (tilghman) 2010-01-25 18:16:30.000-0600 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. By: Digium Subversion (svnbot) 2010-02-01 12:38:38.000-0600 Repository: asterisk Revision: 244151 U branches/1.4/res/res_features.c ------------------------------------------------------------------------ r244151 | tilghman | 2010-02-01 12:38:37 -0600 (Mon, 01 Feb 2010) | 8 lines When a transferer hangs up during an attended transfer BEFORE the transfer is answered, don't stop playing MOH. (closes issue ASTERISK-15367) Reported by: litnimax Patches: atxfer_moh_16513.patch uploaded by gknispel proformatique (license 261) Tested by: litnimax ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=244151 By: Digium Subversion (svnbot) 2010-02-01 12:39:33.000-0600 Repository: asterisk Revision: 244154 _U trunk/ ------------------------------------------------------------------------ r244154 | tilghman | 2010-02-01 12:39:33 -0600 (Mon, 01 Feb 2010) | 14 lines Blocked revisions 244151 via svnmerge (fixed a different way in trunk and 1.6.x) ........ r244151 | tilghman | 2010-02-01 12:38:37 -0600 (Mon, 01 Feb 2010) | 8 lines When a transferer hangs up during an attended transfer BEFORE the transfer is answered, don't stop playing MOH. (closes issue ASTERISK-15367) Reported by: litnimax Patches: atxfer_moh_16513.patch uploaded by gknispel proformatique (license 261) Tested by: litnimax ........ ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=244154 |