[asterisk-bugs] [JIRA] Commented: (ASTERISK-19949) app_meetme unable to write frame to Local/XXX channel (stuck channel)

[Johan Wilfer (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197770#comment-197770 ] 

Johan Wilfer commented on ASTERISK-19949:
-----------------------------------------

Updated issue and added chan_local as a component. 

This looks like a similar issue: ASTERISK-20486
Matt: Could both be a result of a ref count leak?

> app_meetme unable to write frame to Local/XXX channel (stuck channel)
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-19949
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19949
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_meetme, Channels/chan_local
>    Affects Versions: 1.8.12.1
>         Environment: Debian 6.0 i386 (kernel 2.6.32-5-686-bigmem)
>            Reporter: Johan Wilfer
>         Attachments: myDebugLog.gz
>
>
> I've been watching ASTERISK-19594 as I've seen similar behavior in Asterisk 1.4, but not the infinite loop described in the issue.
> But for a week ago I experienced the exact same issue with to Local channels originated into a conference - stuck channels that generates a lot of rows in the logs. This was Asterisk 1.6.2.22. The proposed fix in the issue was revision 357761 so I upgraded to asterisk 1.8.12.1 tonight.
> So this does not fix the issue!
> I see the same behavior..:
> {code:xml}
> [Jun  1 11:24:57] WARNING[4595] app_meetme.c: Unable to write frame to channel Local/335 at conference_announce_event_connect_room-aca9;2
> [Jun  1 11:24:57] WARNING[11385] app_meetme.c: Unable to write frame to channel Local/224 at conference_announce_event_connect_room-5a80;2
> [Jun  1 11:24:57] WARNING[19214] app_meetme.c: Unable to write frame to channel Local/345 at conference_announce_event_connect_room-997e;2
> [Jun  1 11:24:57] WARNING[12623] app_meetme.c: Unable to write frame to channel Local/403 at conference_announce_event_connect_room-2886;2
> [Jun  1 11:24:57] WARNING[4595] app_meetme.c: Unable to write frame to channel Local/335 at conference_announce_event_connect_room-aca9;2
> [Jun  1 11:24:57] WARNING[11385] app_meetme.c: Unable to write frame to channel Local/224 at conference_announce_event_connect_room-5a80;2
> [Jun  1 11:24:57] WARNING[19214] app_meetme.c: Unable to write frame to channel Local/345 at conference_announce_event_connect_room-997e;2
> [Jun  1 11:24:57] WARNING[12623] app_meetme.c: Unable to write frame to channel Local/403 at conference_announce_event_connect_room-2886;2
> [Jun  1 11:24:57] WARNING[4595] app_meetme.c: Unable to write frame to channel Local/335 at conference_announce_event_connect_room-aca9;2
> [Jun  1 11:24:57] WARNING[11385] app_meetme.c: Unable to write frame to channel Local/224 at conference_announce_event_connect_room-5a80;2
> core show channels verbose
> Local/335 at conference conference_announce_ 335                 3 Up     MeetMe       335,dq                                    02:32:17
> Local/345 at conference conference_announce_ 345                 3 Up     MeetMe       345,dq                                    00:35:21
> Local/224 at conference conference_announce_ 224                 3 Up     MeetMe       224,dq                                    02:25:23
> Local/403 at conference conference_announce_ 403                 3 Up     MeetMe       403,dq                                    00:08:28
> {code} 
> One of the channels are connected to a Meetme, and one are used to announce in the conference. As the announcing channel exit, sometimes the other end that are connected to Meetme experience the above behavior. This seems to be happening after a day or two
> I've tried applying the patch meetme-hangup-trunk-360459.patch in issue ASTERISK-19594 as the next step. I'll report back the progress. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira