<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [Asterisk-Users] Zap FXO channel locked up with steadystatic(white noise)</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2> </FONT>
</P>
<P><FONT SIZE=2>A similar problem just occurred to my Asterisk system last week for the first time. I had been running version 1.0 RC and then 1.0 release with no problem for the last two months. Then last week I upgraded to 1.0.2 and two days later we were doing an 8 party conference via PRI connection on a T100P and about 20 minutes into the conference I heard a short, soft "beep" and was disconnected (everyone was disconnected). Upon trying to call back into the meetme application it answered asked for the conf # and Pin, then connected to steady static. We ended up having to reboot the server to fix. I have since downgraded to 1.0 have not seen the problem occur again. Is there a known problem that would cause this in 1.0.2?</FONT></P>
<BR>
<BR>
<BR>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: asterisk-users-bounces@lists.digium.com [<A HREF="mailto:asterisk-users-bounces@lists.digium.com">mailto:asterisk-users-bounces@lists.digium.com</A>] On Behalf Of Richard Scobie</FONT></P>
<P><FONT SIZE=2>Sent: Monday, November 08, 2004 12:33 AM</FONT>
<BR><FONT SIZE=2>To: Asterisk Users Mailing List - Non-Commercial Discussion</FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Users] Zap FXO channel locked up with steadystatic(white noise)</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>Damon Estep wrote:</FONT>
<BR><FONT SIZE=2>>>I'm having the same problem on my TDM40B (FXS). Unloading and loading </FONT>
<BR><FONT SIZE=2>>>the modules seems to fix it temporally. Digium is sending me a </FONT>
<BR><FONT SIZE=2>>>replacement.</FONT>
<BR><FONT SIZE=2>>>Hopefully that will fix it. </FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I plan to call tech support and see what they have to say, hopefully </FONT>
<BR><FONT SIZE=2>> it is just defective and not un-reliable. Have you heard other </FONT>
<BR><FONT SIZE=2>> complaints of the same thing?</FONT>
</P>
<P><FONT SIZE=2>I have had the same issues with the FXO modules on systems that have run fine for a year using X100Ps. Rebooting the box has been required to fix it.</FONT></P>
<P><FONT SIZE=2>Please let us know what Digium tell you.</FONT>
</P>
<P><FONT SIZE=2>Regards,</FONT>
</P>
<P><FONT SIZE=2>Richard</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>Asterisk-Users mailing list</FONT>
<BR><FONT SIZE=2>Asterisk-Users@lists.digium.com</FONT>
<BR><FONT SIZE=2><A HREF="http://lists.digium.com/mailman/listinfo/asterisk-users" TARGET="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</A></FONT>
<BR><FONT SIZE=2>To UNSUBSCRIBE or update options visit:</FONT>
<BR><FONT SIZE=2> <A HREF="http://lists.digium.com/mailman/listinfo/asterisk-users" TARGET="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</A></FONT>
</P>
</BODY>
</HTML>