<br><br><div class="gmail_quote">On Jan 16, 2008 7:07 PM, Russell Bryant <<a href="mailto:russell@digium.com">russell@digium.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Steven wrote:<br>> I'm not sure what to try next, other than calling the telco and asking<br>> them to check their equipment. Does any one have a suggestion before I<br>> do that?<br><br>
</div>I have a suggestion. Have you contacted Digium technical support for assistance<br>with resolving this issue?<br><font color="#888888"><br>--<br>Russell Bryant<br>Senior Software Engineer<br>Open Source Team Lead<br>
Digium, Inc.<br></font><div></div></blockquote><div><br>Excellent suggestion. Make sure you can give them SSH access and screen so you can see what they are doing. Before that, check (remake) your T1 cables and if it is punched down on a block, re-punch it.
<br><br>Work with your telco as well. I call that burning the candle from both ends. You said there were no errors looping port one to port two and generating calls with call files. That may indicate a telco issue. I usually open a ticket with the telco right away just in case so it can be escalated quicker if in fact it is the telco. Sometimes you have to be a jerk to these guys to get someone with half a brain to look into your problem rather than blaming CPE (the easiest way to close their ticket and get you off the phone).
<br><br>If Digium says it is the telco and the telco says it is your CPE (Asterisk/Digium/Server/CPE wiring) then put them together on a conference call! <br><br>I am sure it won't come to that if it is truly a Digium/Asterisk issue. They will take care of it.
<br><br>Thanks,<br>Steve Totaro<br></div></div><br>