Layer 1 is fine.<br><br>So, we have either a layer 2 or 3 issue.<br><br>Now, a quick primer on connectivity to the ISDN switch.<br><br>Your Router is connected, via layer 1, from the WIC, to a Smartjack (the thingy on the wall at the premise), the T1 carrier brings layer 1 to the telephone company's Central Office (with repeaters in the middle) into a Digital Access Cross Connect (aka a DACS, commercially known as a Titan)... from there, your PRI is demultiplexed (or multiplexed, depending on whether the telco is agregating T1s) over to a local type 4 (or 5) switch, or trunked to another Central Office.
<br><br>Based on the output you have sent, we know that we are fine all the way to the DACS (otherwise we would see errors on the controller).<br><br>Since we are seeing no slips, we also know that we are getting good clock from the ISDN switch itself.
<br><br>What we are not seeing is any reply from the ISDN switch (hence the "user TX -> SABMEp sapi=0 tei=0" but no " User RX <- RRf sapi=0 tei=0 nr=32" or similar)<br><br>So, the problem is on the ISDN switch itself. Either it has no idea what you are talking about (wrong switch-type, which is unlikely since it used to work).
<br><br>Engage the carrier and escalate hourly.<br><br><br><br><br>Jonathan<br><br><div><span class="gmail_quote">On 11/21/06, <b class="gmail_sendername">Robert Kulagowski</b> <<a href="mailto:bob@smalltime.com">bob@smalltime.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Jonathan Charles wrote:<br>> I would start by checking the t1 controller for errors, is it up, etc.
<br><br>T1 0/2/0 is up.<br> Applique type is Channelized T1<br> Cablelength is long gain36 0db<br> No alarms detected.<br> alarm-trigger is not set<br> Soaking time: 3, Clearance time: 10<br> AIS State:Clear LOS State:Clear LOF State:Clear
<br> Version info Firmware: 20060711, FPGA: 13, spm_count = 0<br> Framing is ESF, Line Code is B8ZS, Clock Source is Line.<br> CRC Threshold is 320. Reported from firmware is 320.<br> Data in current interval (208 seconds elapsed):
<br> 0 Line Code Violations, 0 Path Code Violations<br> 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins<br> 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs<br> Total Data (last 24 hours)
<br> 0 Line Code Violations, 0 Path Code Violations,<br> 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,<br> 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs<br><br>Currently configuring SIP, so no
H.323 or MGCP.<br><br>deb isdn standard is showing essentially the same thing as I pasted in<br>my first email.<br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br>