meetme – Unable to write frame to channel

WARNING: this is an automatic post retrieved from the Asterisk-Users Mailing List, not an authored post Mailing-list Collector January 20, 2012 Asterisk Users 3 Comments

Tags: , , , , , , ,

Hi,

Once in a while when a SIP channel connected to meetme conference is hung up, I start getting the following error multiple times:

WARNING[14031]: app_meetme.c:3668 conf_run: Unable to write frame to channel Local/100203@h

The status of the channel is not updated, and the only way to get back to normal is to restart Asterisk.

Any thoughts? Is this a timing issue?

Thanks a lot,
Matt

You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

3 Responses to “meetme – Unable to write frame to channel”

  1. Matt Hamilton said:

    Jan 21, 12 at 10:32 am

    Other posts on the internet suggests that this is a timing issue.

    According to Asterisk wiki, the preferred timing module is res_timing_timerfd.so (then res_timing_dahdi.so and the least preferred res_timing_pthread.so).

    res_timing_timerfd.so is the one I’m using, but still getting these errors. Is timing hardware such as TDM410P, Sangoma UT51, the only reliable option?

    Thanks.

    Hi,

    Once in a while when a SIP channel connected to meetme conference is hung up, I start getting the following error multiple times:

    WARNING[14031]: app_meetme.c:3668 conf_run: Unable to write frame to channel Local/100203@h

    The status of the channel is not updated, and the only way to get back to normal is to restart Asterisk.

    Any thoughts? Is this a timing issue?

    Thanks a lot,
    Matt

  2. Johan Wilfer said:

    Jan 22, 12 at 8:36 am

    2012-01-20 20:09, Matt Hamilton skrev:

    As you write I have seen this also with SIP in Meetme conferences
    sometimes when sip-channels is hung up.
    I havn’t found any real problem or bad sound related to this, so I
    usually ignore this error.

  3. Matt Hamilton said:

    Jan 22, 12 at 1:24 pm

    I’m not using meetme directly – I’m using SLA which internally uses meetme and creates conferences for SLA trunks. There are no sound problems for me, either, but when the caller hangs up and this error occurs, the trunk statuses are not updated properly and the phones still show them as in use or hold.

    It’s really hard to duplicate it – it seems to happen more under heavier load though.

    Matt

    2012-01-20 20:09, Matt Hamilton skrev:

    Hi,

    Once in a while when a SIP channel connected to meetme
    conference is hung up, I start getting the following error
    multiple times:

    WARNING[14031]: app_meetme.c:3668 conf_run: Unable to write
    frame to channel Local/100203@h

    The status of the channel is not updated, and the only way to
    get back to normal is to restart Asterisk.

    Any thoughts? Is this a timing issue?

    As you write I have seen this also with SIP in Meetme conferences
    sometimes when sip-channels is hung up.

    I havn’t found any real problem or bad sound related to this, so I
    usually ignore this error.