Unable to write frame to channel

I recently upgraded to a new new server and also moved to CentOs 6 and Asterisk 1.8. The new server allowed me to set up MeetMe conferences which I did not have set up before. Frequently when a channel connected to a MeetMe conference is hung up I get the below error. The error continues to be logged many times per second until I either shut down asterisk or kick the user from the conference. Asterisk seems to continue running while the error messages are logged. The error happens with both IAX2 and SIP channels.

Can anyone please help with this?

[Jan 12 02:53:45] WARNING[11076] app_meetme.c: Unable to write frame to channel SIP/202-0000000f [Jan 12 02:53:45] WARNING[11076] app_meetme.c: Unable to write frame to channel SIP/202-0000000f [Jan 12 02:53:45] WARNING[11076] app_meetme.c: Unable to write frame to channel SIP/202-0000000f [Jan 12 02:53:45] WARNING[11076] app_meetme.c: Unable to write frame to channel SIP/202-0000000f [Jan 12 02:53:45] WARNING[11076] app_meetme.c: Unable to write frame to channel SIP/202-0000000f

CentOs 6.2 x86_64
Asterisk 1.8.7.1

Raymond

Hi Raymond,

Were you able to resolve this issue? I have the same setup as you - Centos 6 and Asterisk 1.8, and have exactly the same problem.

Older posts suggests that this might be a timing issue - meetme seems to require a timing device and dahdi. I’m using res_timing_timerfd.so as recommended in Asterisk wiki, but still having the same issue.

Best Regards,
Matt

Hi, Matt. Raymond

I too have the same problem. I’ve found that my conference will support as many internal users as I’ve got phones (10). But the:
Unable to write frame to channel
problem occurs and fills up the log files when I get a 3rd external user to join the MeetMe conference.

Asterisk 1.8.8.0 built by root @ pbx.local on a i686 running Linux on 2012-02-10 12:15:38 UTC

and MeetMe 2.10.0.3

I’m running virtual with reasonable resources.

Regards

Andy

We’re also seeing this issue on our server, hadn’t noticed that it only starts when 3 people join a conference room, but that could be a link. We find at the moment we need to manually reboot our server once a week to stop the logs becoming redundant.

I think this issue may be related to another problem I have posted about previously:

forums.asterisk.org/viewtopic.php?f=1&t=82505

Essentially when we use conference rooms after a while the entry message will advise that there is someone there who isn’t. (i.e. “there are 3 people in this conference” when there are only 2)