<div>I've just encountered an odd problem with our Digium TE410P card and was wondering if anyone has experienced something similar before. </div><div><br></div><div>We utilize all 4 ports with 2 of them connected to the PSTN as E1 with the second 2 ports connecting to a device which accepts T1. We are essentially acting as an E1 to T1 converter. This machine has been operational for close to 6 months without a problem. </div>
<div><br></div><div>Today after restarting the box after a scheduled power outage none of the spans on the TE410P were coming up. All were reporting RED alarms. Nothing had changed on the server and nothing had been changed at the telco side. </div>
<div><br></div><div>We quickly removed the card and checked the jumpers, suspecting that it may somehow have 'changed' it's state. Checking the card showed that all ports were open, which is what we expected. Re-setting the card done nothing to resolve our problem. </div>
<div><br></div><div>We tested the line from the telco by connecting to our PBX, which can accept a T1 connection. This worked fine, ruling out any telco based problems. </div><div><br></div><div>lspci showed that the card was being detected and 'zap show status' showed all the spans and channels configured as they should have been. Testing the ports and observing how things were behaving with our PBX it appeared that the TE410P ports were able to send out a signal, but for some reason, it could not accept a signal. </div>
<div><br></div><div>After some trial and error, and more than a few reboots we finally found a solution of sorts. Here is what we had to do: </div><div><br></div><div>* Power down the machine</div><div>* Disconnect all cables from the ports</div>
<div>* Power up</div><div>* After everything has started up again re-connect the ports</div><div><br></div><div>This resulted in all the ports going green and becoming operational. </div><div><br></div><div>Has anyone every experienced this or something similar before? Everything is working fine now, but I would rather not have to visit our data centers everytime we have to power cycle one of our machines. Could this be a config issue in the way the zaptel driver is loaded? </div>
<div><br></div><div>Here are the versions we are running: </div><div><br></div><div>Asterisk 1.4.18.1</div><div>Zaptel 1.4.9.2-48</div><div>Libpri 1.4.3-19</div><div><br></div><div>This is all bundled in the SME Server SARK distrubution. I can provide a copy of our zapata/zaptel configs if necessary. </div>
<div><br></div><div>Any ideas/pointers/anecdotes welcomed, </div><div><br>Cheers, </div><div><br></div><div>Conor</div>