Hi Matthew, 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... 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? Thanks Darren On 23/08/06, Matthew Fredrickson <creslin@xxxxxxxxxx> wrote: > > > On Aug 22, 2006, at 6:10 PM, Storer, Darren wrote: > > I've been trying to get a signalling link up from a test libss7 build > > to an ISUP (White Book) Simulator/Emulator. The Asterisk box is using > > an old E100P single E1 card with a cross over cable to the simulator. > > After loading zaptel and wct1xxp I have started Asterisk and layer 1 > > is good (loss of signal and remote alarm functions work > > asexpected).The bad news is thatIcannot see any SIO/SIOS messages > > being returned from the libss7 machine. > > > > To prove the I/O from the SS7 simulator I have looped backits E1 and > > watched as the link starts to emergency align but it fails > > (obviously)because the point codes clash when the signalling link > > test messages (SLTM) are sent. > > > > The question is, does anyone know if there any debug facilities > > available within libss7? It's much to early to expect something > > similar to the 'pri debug' command but hopefully there is something > > that will help to show what libss7 is transmitting and receiving. > > Also, ifa goodlibss7 build is looped back on itself will it start to > > align and write messages into a log file or to the Asterisk console? > > > > Just in case I have made a mess of the libss7 configuration I have > > uploadeda copy of the config files and span status here: > > > > http://www.comgate.co.uk/libss7 > > Hey! I thought I had replied to your message already, but there goes > again. You can turn on debug by the "ss7 debug linket x" command at > the console. It will give you some debug output that is useful. Also, > you can try the ss7linktest program that is in the libss7 directory to > get a verbose debug output of what is happening on link initialization. > You can change your point code selection on the real system in the > zapata.conf. pointcode is the local point code, adjpointcode is the > point code used in the SLTM messages, and defaultdpc is the point code > used as the destination for ISUP (layer4) messages. > > Matthew Fredrickson -- > Darren Storer > Comgate > Telco|Internet|Broadcast -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-ss7/attachments/20060822/90baf3a2/attachment.htm
|