[asterisk-dev] ASTERISK-19594 - Stuck channels inside meetme

[Johan Wilfer]

Hello,

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. (
https://issues.asterisk.org/jira/browse/ASTERISK-19594 )

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.

But now I see the same behavior..:

[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


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 for my customer.


It seems like I can't create new comments on ASTERISK-19594, should I
clone the issue or create a new one?


-- 
Johan Wilfer                 email: johan at jttech.se
JT Tech | Developer          webb: http://jttech.se