[Asterisk-code-review] bridge: stuck channel(s) after failed attended transfer (asterisk[13])
Kevin Harwell
asteriskteam at digium.com
Wed Jun 21 11:17:27 CDT 2017
Hello Richard Mudgett, Jenkins2,
I'd like you to reexamine a change. Please visit
https://gerrit.asterisk.org/5892
to look at the new patch set (#2).
Change subject: bridge: stuck channel(s) after failed attended transfer
......................................................................
bridge: stuck channel(s) after failed attended transfer
If an attended transfer failed it was possible for some of the channels
involved to get "stuck" because Asterisk was not hanging up the transfer target.
This patch ensures Asterisk hangs up the transfer target when an attended
transfer failure occurs.
ASTERISK-27075 #close
Change-Id: I98a6ecd92d3461ab98c36f0d9451d23adaf3e5f9
---
M main/bridge.c
1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://gerrit.asterisk.org:29418/asterisk refs/changes/92/5892/2
--
To view, visit https://gerrit.asterisk.org/5892
To unsubscribe, visit https://gerrit.asterisk.org/settings
Gerrit-Project: asterisk
Gerrit-Branch: 13
Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I98a6ecd92d3461ab98c36f0d9451d23adaf3e5f9
Gerrit-Change-Number: 5892
Gerrit-PatchSet: 2
Gerrit-Owner: Kevin Harwell <kharwell at digium.com>
Gerrit-Reviewer: Jenkins2
Gerrit-Reviewer: Richard Mudgett <rmudgett at digium.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-code-review/attachments/20170621/cb81f992/attachment.html>
More information about the asterisk-code-review
mailing list