From: Kevin Harwell <kharwell@digium.com>
Date: Tue, 7 Apr 2015 16:40:44 +0000 (+0000)
Subject: bridge.c: Hangup attended transfer target after it has been swapped out
X-Git-Tag: certified/13.1-cert7~13^2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c8e21c4eb9b1131ab6c4d2107d7ad42485394501;p=thirdparty%2Fasterisk.git

bridge.c: Hangup attended transfer target after it has been swapped out

After completing an attended transfer the transfer target channel (the one that
gets swapped out) was not being hung up after leaving the bridge. This resulted
in a channel possibly being left around. Added an explicit softhangup for the
channel in question after the transfer is successfully completed in order to
make sure the channel is hung up.

ASTERISK-24782 #close
Reported by: John Bigelow
Review: https://reviewboard.asterisk.org/r/4575/

This patch is a remedial cherry-pick from v13.

Change-Id: I26cc0c207acf74ade93e6567febf7b9776452058
---

diff --git a/main/bridge.c b/main/bridge.c
index c1729e55ca..f621942cec 100644
--- a/main/bridge.c
+++ b/main/bridge.c
@@ -4540,6 +4540,7 @@ enum ast_transfer_result ast_bridge_transfer_attended(struct ast_channel *to_tra
 		ast_bridge_unlock(to_transferee_bridge);
 		ast_bridge_unlock(to_target_bridge);
 
+		ast_softhangup(to_transfer_target, AST_SOFTHANGUP_DEV);
 		goto end;
 	}