[asterisk-bugs] [JIRA] (ASTERISK-26083) ARI: Announcer channels staying around after playback to a bridge is finished

[Per Jensen (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Per Jensen updated ASTERISK-26083:
----------------------------------

    Attachment: asterisk_log.txt

> ARI: Announcer channels staying around after playback to a bridge is finished
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-26083
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26083
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.9.1
>            Reporter: Per Jensen
>         Attachments: asterisk_log.txt
>
>
> h1. Summary
> When using the {{play}} feature on a bridge, the announcer channel does not go away when the playback is finished or when the bridge is destroyed.
> After the first sound has finished playing, all subsequent attempts to play tones or sounds to the bridge will fail with a '500 - Internal Server Error, Allocation Failed'
> I have not noticed this issue prior to version 13.9.1
> Log file is an example of the issue
> h1. Steps I use to reproduce.
> 1. Start Stasis app with a PJSIP channel
> 2. Create bridge of type 'simple_mixing'
> 3. Add channel to bridge
> 4. Use [play|https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Bridges+REST+API#Asterisk13BridgesRESTAPI-play] from the bridges REST API to play "tone:ring"
> 5. Stop the tone
> 6. Play "tone:congestion" (or really any other tone) - 500 happens here 
> 7. Hang up channel
> 8. Destroy bridge
> 9. Exit stasis
> The announcer channel will still be there.



--
This message was sent by Atlassian JIRA
(v6.2#6252)