[Home]

Summary:ASTERISK-04379: [patch] Don't transfer to busy tone in a three-way call. (chan_zap.c)
Reporter:Thomas (thomas andrews)Labels:
Date Opened:2005-06-09 01:55:20Date Closed:2008-01-15 15:37:56.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) busy-no-xfer.patch
( 1) busy-no-xfer-2.patch
( 2) busy-onhk-no-xfer-2.patch
Description:Assume you have an established call, and then make an enquiry call to a third party which turns out to be busy. If you then go on-hook, the party on hold would be connected to busy-tone. This patch changes that behaviour: going on hook simply terminates the enquiry call, and rings your phone so that when you go off-hook you are once again connected to the party on hold.
Comments:By: Thomas (thomas andrews) 2005-06-09 06:53:45

This patch breaks call transfer. Please ignore it! Sorry for submitting it prematurely. Please close this bug. Again sorry!
By: Thomas (thomas andrews) 2005-06-09 09:39:33

I've uploaded an improved patch - tested a bit better this time. It also handles the case where Recall gets pressed while listening to busy tone, with a caller on hold. (much the same as above but with Recall instead of on-hook.)
By: Kevin P. Fleming (kpfleming) 2005-06-09 18:22:05

I like it... it's a big improvement. Committed to CVS HEAD, thanks!
By: Digium Subversion (svnbot) 2008-01-15 15:37:56.000-0600

Repository: asterisk
Revision: 5892

U   trunk/channels/chan_zap.c

------------------------------------------------------------------------
r5892 | kpfleming | 2008-01-15 15:37:55 -0600 (Tue, 15 Jan 2008) | 2 lines

make zap-transfers to busy/congestion channels behave more reasonably (bug ASTERISK-4379)

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=5892