[asterisk-bugs] [JIRA] (ASTERISK-19491) MeetMe fails to remove participant from conference when user leaves during playback of 'conf-onlyperson.ulaw'

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-19491:
-----------------------------------

    Target Release Version/s: 11.2.0
                              10.12.0-digiumphones
                              10.12.0
                              1.8.20.0
    
> MeetMe fails to remove participant from conference when user leaves during playback of 'conf-onlyperson.ulaw'
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19491
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19491
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_meetme
>    Affects Versions: 1.8.7.2, 1.8.10.0
>         Environment: Ubuntu Linux latest
> kernel  3.0.0-12-server #20-Ubuntu SMP 
> x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Andrew
>            Assignee: Andrew
>            Severity: Minor
>      Target Release: 1.8.20.0, 10.12.0, 10.12.0-digiumphones, 11.2.0
>
>         Attachments: Asterisk debug log
>
>
> When calling the Meetme() application if you hangup on the initial prompt it floods the CLI with these messages endlessly:
> Unable to write frame to channel SIP/7081053DA9E1-00000000
> Unable to write frame to channel SIP/7081053DA9E1-00000000
> If I call it back again, I get a tone as though I'm the second person in the conference call. When I hang up again it then destroys the conference and then stops the messages. 
> I'm able to reproduce this every time. I had this issue on 1.8.7 and then upgraded to 1.8.10 to see if the issue was resolved before reporting it. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira