| Summary: | ASTERISK-24637: Channel re-enters Stasis() when it should not | ||
| Reporter: | John Bigelow (jbigelow) | Labels: | |
| Date Opened: | 2014-12-22 14:17:19.000-0600 | Date Closed: | 2015-01-09 15:47:01.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Bridges/bridge_simple Bridges/bridge_softmix Core/Bridging Resources/res_ari_bridges Resources/res_ari_channels Resources/res_stasis |
| Versions: | SVN 13.1.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Asterisk branch 13 r429984 | Attachments: | ( 0) extensions.conf ( 1) full.txt ( 2) test-config.yaml |
| Description: | A channel pulled out of a stasis bridge and into another bridge via app_bridge is re-entered into Stasis() after the bridged channel is hung up. According to the following test plan, the channel should not re-enter Stasis and instead should continue at the next priority being to execute the UserEvent() app in this set up.
https://wiki.asterisk.org/wiki/pages/viewpage.action?pageId=30279826#StasisStart/StasisEndTestplan-Bridge()DialplanApplication # Channel A enters Stasis() # Stasis bridge is created # Channel A is added to stasis bridge # Channel B enters Bridge(channel A) # Channel A is pulled out of stasis bridge and Stasis() app # Channel A enters non-stasis bridge # Channel B enters non-stasis bridge # Channel B hangs up # Channel A re-enters Stasis(). IE. Where it was when it was pulled out and put into the non-stasis bridge | ||
| Comments: | |||