<font class="Apple-style-span" face="arial, helvetica, sans-serif">Hi <span class="Apple-style-span" style="border-collapse: collapse; "><font size="2"><font size="2">José,</font></font></span></font><div><font class="Apple-style-span" face="arial, helvetica, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, helvetica, sans-serif"><font size="2"><font size="2"></font></font><span class="Apple-style-span" style="border-collapse: collapse;">have you checked that the Telco clocking is provided on the correct timeslot and that the SS7 signalling from the Telco is on the same timeslot as your Asterisk system is expecting?</span></font></div>
<div><font class="Apple-style-span" face="arial, helvetica, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse; "><br></span></font></div><div><font class="Apple-style-span" face="arial, helvetica, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">If you have an ISDN tester with audio monitor, you can listen for the presence of SS7 signalling (sounds like buzzing) by selecting each CIC (timeslot) sequentially.</span></font></div>
<div><font class="Apple-style-span" face="arial, helvetica, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, helvetica, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Regards</span></font></div>
<div><font class="Apple-style-span" face="arial, helvetica, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse; "><br>Darren</span></font></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; border-collapse: collapse; color: rgb(153, 153, 153); "><b> </b></span></div>
<div><div><br><div class="gmail_quote">2011/1/25 José Pablo Méndez Soto <span dir="ltr"><<a href="mailto:auxcri@gmail.com">auxcri@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="gmail_quote"><div>Hi,<br><br>We need assistance aligning 8 E1 ports (2x Digium Quad Span TE410P) with our TELCO.<br></div><div><br></div><div>We are working on a relatively big SS7 deployment for some time now. We are using:<br>
<br> </div><div>
asterisk-1.8.2.1<br>asterisk-addons-1.6.2.<br>dahdi-linux-complete-2.4.0+2.4.0<br>libss7-1.0.2<br><br>So far, we think that we should start sending and receiving SIO messages to establish a layer 2 connection.<br><br></div>
<div>We currently have just two E1 ports connected to our TELCO. Layer 1 looks good so far. We have both cards OK and neither the TELCO nor our server report any alarms.</div>
<div><br></div><div>T4XXP (PCI) Card 1 Span 1 OK 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1)</div><div>T4XXP (PCI) Card 1 Span 2 OK 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1)</div>
<div><br></div><div>We are having problems to pass by the NOTALIGNED STATE.</div><div><br></div><div>The carrier asked us to configure the last channel as the D channel on both spans (31, or 155 and 186 in our case).</div>
<div><br></div><div>Here is an extract of "lsdahdi"</div><div><br></div><div>### Span 5: TE4/1/1 "T4XXP (PCI) Card 1 Span 1" (MASTER) HDB3/CCS</div><div>...</div><div>155 PRI MTP2 (In use) (SWEC: MG2)</div>
<div><br></div><div>### Span 6: TE4/1/2 "T4XXP (PCI) Card 1 Span 2" HDB3/CCS</div><div>186 PRI MTP2 (In use) (SWEC: MG2)</div><div><br></div><div>We can see upon load of the chan_dahdi.so the modules get loaded and the channels are registered as SS7 signaling.</div>
<div><br></div><div> -- Registered channel 125, SS7 signalling</div><div> -- Registered channel 125, SS7 signalling</div><div> -- Registered channel 126, SS7 signalling</div>
<div><span style="white-space:pre-wrap"> </span></div><div>We run a ss7 set debug on linktest 1 and we see SIO messages going out ( at least I see > ) If this angle bracket doesn´t mean "out" please someone correct me.<br>
</div>
<div><span style="white-space:pre-wrap"> </span></div><div>We don´t seem to have any SIO back, so we get stuck at this point where the T2 timer expires we go back to IDLE.<span style="white-space:pre-wrap"> </span></div>
<div><span style="white-space:pre-wrap"> </span></div><div><span style="white-space:pre-wrap"> </span>{1] Link state change: IDLE -> NOTALIGNED</div><div>[1] Link state change: NOTALIGNED -> IDLE</div>
<div>[1] Link state change: IDLE -> NOTALIGNED</div><div>[1] Link state change: NOTALIGNED -> IDLE</div><div>[1] Link state change: IDLE -> NOTALIGNED</div><div>[1] Len = 4 [ ff ff 01 00 ]</div><div>[1] FSN: 127 FIB 1</div>
<div>[1] BSN: 127 BIB 1</div><div>[1] >[0] LSSU SIO</div><div>[1]</div><div>[1] Len = 4 [ ff ff 01 00 ]</div><div>[1] FSN: 127 FIB 1</div><div>[1] BSN: 127 BIB 1</div><div>[1] >[1] LSSU SIO</div><div>[1]</div><div>
[1] Link state change: NOTALIGNED -> IDLE</div>
<div>[1] Link state change: IDLE -> NOTALIGNED</div><div>[1] Link state change: NOTALIGNED -> IDLE</div><div>[1] Link state change: IDLE -> NOTALIGNED</div><div><br><br>Compiling dahdi_pcap helped us a lot. Can some one please confirm from the 2 packet captures below, if the SIO and SIOS messages are incoming, as I see from the "Point-to-Point Direction: Received (1)" lines?:<br>
<br>No. Time Source Destination Protocol Info<br> 2 0.536890 MTP2 SIO<br><br>Frame 2 (6 bytes on wire, 6 bytes captured)<br> Arrival Time: Jan 24, 2011 17:48:55.106277000<br>
[Time delta from previous captured frame: 0.536890000 seconds]<br> [Time delta from previous displayed frame: 0.536890000 seconds]<br> [Time since reference or first frame: 0.536890000 seconds]<br> Frame Number: 2<br>
Frame Length: 6 bytes<br> Capture Length: 6 bytes<br> [Frame is marked: False]<br> [Protocols in frame: mtp2]<br> Point-to-Point Direction: Received (1)<br> Link Number: 155<br>Message Transfer Part Level 2<br>
.111 1111 = Backward sequence number: 127<br> 1... .... = Backward indicator bit: 1<br> .111 1111 = Forward sequence number: 127<br> 1... .... = Forward indicator bit: 1<br> ..00 0001 = Length Indicator: 1<br>
00.. .... = Spare: 0<br> Status field: Status Indication O (0)<br><br>No. Time Source Destination Protocol Info<br> 3 33.532990 MTP2 SIOS<br>
<br>Frame 3 (6 bytes on wire, 6 bytes captured)<br> Arrival Time: Jan 24, 2011 17:49:28.102377000<br> [Time delta from previous captured frame: 32.996100000 seconds]<br> [Time delta from previous displayed frame: 32.996100000 seconds]<br>
[Time since reference or first frame: 33.532990000 seconds]<br> Frame Number: 3<br> Frame Length: 6 bytes<br> Capture Length: 6 bytes<br> [Frame is marked: False]<br> [Protocols in frame: mtp2]<br> Point-to-Point Direction: Received (1)<br>
Link Number: 155<br>Message Transfer Part Level 2<br> .111 1111 = Backward sequence number: 127<br> 1... .... = Backward indicator bit: 1<br> .111 1111 = Forward sequence number: 127<br> 1... .... = Forward indicator bit: 1<br>
..00 0001 = Length Indicator: 1<br> 00.. .... = Spare: 0<br> Status field: Status Indication OS (3)<br></div><br><br>These are some debug lines:<br>[Jan 24 22:42:18] ERROR[1528]: chan_dahdi.c:13534 dahdi_ss7_error: [1] Received MSU in invalid state 1<br>
[Jan 24 22:42:18] ERROR[1528]: chan_dahdi.c:13534 dahdi_ss7_error: [1] Received MSU in invalid state 1<br>con hardhdlc<br>[Jan 24 23:09:26] ERROR[1283]: chan_dahdi.c:13534 dahdi_ss7_error: [1] Received MSU in invalid state 1<br>
[1] Got message smaller than the minimum SS7 SU length. Dropping<br>[Jan 24 23:09:26] NOTICE[1283]: chan_dahdi.c:3310 my_handle_link_exception: SS7 got event: HDLC Overrun(7) on span 1/1<br>[Jan 24 23:09:26] NOTICE[1283]: chan_dahdi.c:3310 my_handle_link_exception: SS7 got event: HDLC Overrun(7) on span 1/0<br>
[Jan 24 23:09:26] NOTICE[1283]: chan_dahdi.c:3310 my_handle_link_exception: SS7 got event: HDLC Overrun(7) on span 1/1<br>[Jan 24 23:09:26] NOTICE[1283]: chan_dahdi.c:3310 my_handle_link_exception: SS7 got event: HDLC Bad FCS(8) on span 1/0<br>
[Jan 24 23:09:26] NOTICE[1283]: chan_dahdi.c:3310 my_handle_link_exception: SS7 got event: HDLC Overrun(7) on span 1/1<br>[1] Got message smaller than the minimum SS7 SU length. Dropping<br><br>Attached you will find system.conf, chan_dahdi.conf and dahdi_channels.conf, please if you have any insights what can be going on on these regards, what can we change, or what can be logged for further analysis, it would be very much appreciated.<br>
<br>Also, can somebody explain what these messages in /var/log/messages mean?<br><br>Jan 23 09:23:39 ss7-core kernel: [202529.404359] wct4xxp 0000:03:01.0: All spans in alarm : No validspan to source RCLK from<br><br>And this from /var/log/asterisk?:<br>
<br>[Jan 24 14:26:29] NOTICE[1170] chan_dahdi.c: SS7 got event: HDLC Abort(6) on span 1/0<br>[Jan 24 15:55:30] NOTICE[1170] chan_dahdi.c: SS7 got event: HDLC Abort(6) on span 1/1<br><br><br>Thank you very much in advance,<br>
<br><br>-- <font color="#888888"></font><br clear="all"></div><font color="#888888"><font color="#888888"><b style="color:rgb(153, 153, 153)"><span style="color:rgb(153, 153, 153)"><font size="2"><font size="2"><span style="font-family:verdana,sans-serif"><span style="font-family:trebuchet ms,sans-serif"><span style="font-family:verdana,sans-serif">José Pablo Méndez</span></span></span></font><br>
<img height="40" width="68"> </font></span></b><img height="40" width="40"></font></font></div>
<br>--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-ss7 mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-ss7" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-ss7</a><br></blockquote></div><br></div></div>