<div>Hi Matthew,</div>
<div> </div>
<div>just what I needed to know, thanks for the second reply. I have checked my spam filters but the first reply didn't arrive here...</div>
<div> </div>
<div>I will try out the commands you mentioned in the office tomorrow and hopefully make a little more progress. I am really looking to reassure myself that my libss7 build is working correctly. Will a good libss7 build start to align with itself if its E1 is looped back?
</div>
<div> </div>
<div>Thanks</div>
<div> </div>
<div>Darren<br><br> </div>
<div><span class="gmail_quote">On 23/08/06, <b class="gmail_sendername">Matthew Fredrickson</b> <<a href="mailto:creslin@digium.com">creslin@digium.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>On Aug 22, 2006, at 6:10 PM, Storer, Darren wrote:<br>> I've been trying to get a signalling link up from a test libss7 build
<br>> to an ISUP (White Book) Simulator/Emulator. The Asterisk box is using<br>> an old E100P single E1 card with a cross over cable to the simulator.<br>> After loading zaptel and wct1xxp I have started Asterisk and layer 1
<br>> is good (loss of signal and remote alarm functions work<br>> asexpected).The bad news is thatIcannot see any SIO/SIOS messages<br>> being returned from the libss7 machine.<br>> <br>> To prove the I/O from the SS7 simulator I have looped backits E1 and
<br>> watched as the link starts to emergency align but it fails<br>> (obviously)because the point codes clash when the signalling link<br>> test messages (SLTM) are sent.<br>> <br>> The question is, does anyone know if there any debug facilities
<br>> available within libss7? It's much to early to expect something<br>> similar to the 'pri debug' command but hopefully there is something<br>> that will help to show what libss7 is transmitting and receiving.
<br>> Also, ifa goodlibss7 build is looped back on itself will it start to<br>> align and write messages into a log file or to the Asterisk console?<br>> <br>> Just in case I have made a mess of the libss7 configuration I have
<br>> uploadeda copy of the config files and span status here:<br>> <br>> <a href="http://www.comgate.co.uk/libss7">http://www.comgate.co.uk/libss7</a><br><br>Hey! I thought I had replied to your message already, but there goes
<br>again. You can turn on debug by the "ss7 debug linket x" command at<br>the console. It will give you some debug output that is useful. Also,<br>you can try the ss7linktest program that is in the libss7 directory to
<br>get a verbose debug output of what is happening on link initialization.<br>You can change your point code selection on the real system in the<br>zapata.conf. pointcode is the local point code, adjpointcode is the<br>
point code used in the SLTM messages, and defaultdpc is the point code<br>used as the destination for ISUP (layer4) messages.<br><br>Matthew Fredrickson</blockquote>
<div> </div>
<div> </div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">-- <br>Darren Storer<br>Comgate<br>Telco|Internet|Broadcast </blockquote></div>