| Summary: | ASTERISK-21924: Have the core bridging layer set the channel hang up cause on the channel/peer when the peer/channel breaks the bridge | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
| Date Opened: | 2013-06-19 19:38:04 | Date Closed: | 2013-08-09 12:38:03 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/Bridging |
| Versions: | 12 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Currently the Asterisk bridging core doesn't always set the hangup cause on the channel when it should. This is particularly the case if a peer breaks a bridge by hanging up, and the channel that was bridged with the peer is ejected and needs to be hung up.
Note that this addresses the following BUGBUG comments in the source: * app_dial - /* BUGBUG bridge needs to set hangup cause on chan when peer breaks the bridge. */ * bridging.c - /* BUGBUG need a cause code on the bridge for the later ejected channels. */ * bridging.c - /* BUGBUG need cause code for the bridge_channel leaving the bridge. */ | ||
| Comments: | By: Matt Jordan (mjordan) 2013-08-09 12:38:03.961-0500 This is technically a duplicate of ASTERISK-22042 | ||