Ryan Courtnage
2004-Oct-05 14:48 UTC
[Asterisk-Users] meetme caused 'RTP Read error: Bad file descriptor'
Hi all, Yesterday I had an * server stop working. The triggering event was a caller being transferred to a meetme room: ---snip--- DEBUG[14270483]: Released clone lock on 'SIP/299-731b' DEBUG[14270483]: Done Masquerading SIP/211-8649 (6) DEBUG[14270483]: Ooh, something swapped out under us, starting over WARNING[14270483]: Error getting conference DEBUG[14237713]: Bridge stops because we're zombie or need a soft hangup: c0=SIP/299-093a, c1=SIP/299-731b, flags: No,No,Yes,Yes ---snip--- followed immediately by the following warning repeating _hundreds_of_thousands_ of times (in an 8 second timeframe): ---snip--- WARNING[14270483]: RTP Read error: Bad file descriptor ---snip--- The server is running * 1.0-rc2. Any idea what would cause this? Has anyone else experienced similar behaviour? Thanks Ryan