<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18702"></HEAD>
<BODY>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>18 month's ago I
learn't on Asterisk BootCamp that with the TDM400P and FXO modules to avoid
Slot1.</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>Why? It wasn't
satisfactorily answered for me.</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>The wctdm.c code
also reflects that with the following statement in
'wctdm_voicedaa_check_hook'</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>
/* Try to track issues that plague slot one FXO's */</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>
....</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>In an effort to
understand the problem, I need information under what circumstances
and senarios that the problems happened, and the symptoms.</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>Does anyone remember
details?</FONT></SPAN></DIV>Are the problems documented
anywhere?</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>I opened a bug
yesterday <A
href="https://issues.asterisk.org/view.php?id=15261">https://issues.asterisk.org/view.php?id=15261</A> ,
which corrects the SPI timing to the Si3210/15 Proslic, but does it fix the
Slot 1 FXO problem?. I can't get mine to fail, old code or
patched.</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2
face=Arial></FONT></SPAN> </DIV></FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2
face=Arial><speculation></FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>Are there documented
reasons as to why the original wcfxs.c code was changed (refer bug report
above)? As the original wcfxs.c 'read_8bits' code was right, then it got changed
to incorrect SPI read timing, then later the TDM400P (wctdm.c) came out and
was based on the bad code.</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>This may
be speculation at this stage that the problem with an FXO module in
slot 1, and the incorrect SPI timing in read_8bits is
related.</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009></SPAN><SPAN class=157572710-05062009><FONT
size=2 face=Arial></speculation></FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2 face=Arial>Alec
Davis</FONT></SPAN></DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=157572710-05062009><FONT size=2
face=Arial></FONT></SPAN> </DIV></BODY></HTML>