[asterisk-users] meetme - Unable to write frame to channel

[Matt Hamilton]

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


Date: Sun, 22 Jan 2012 13:36:07 +0100
From: lists at jttech.se
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] meetme - Unable to write frame to channel


  


    
  
  
    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 at 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.

    

    

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


--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20120122/32f50485/attachment.htm>