Maybe the cable is connected to the wrong port? On 10/5/07, Matthew Fredrickson <creslin at digium.com> wrote: > Markus A. Wipfler wrote: > > Hi Tobias, > > > > Red Alarm on the card usually indicates a physical problem, I might be > > wrong but check your cabling. > > Yes, I second that. IIRC, in your zapata.conf you had sigchan=1. Zap/1 > is on the first span, and from your output, it looks like span 1 is in > red alarm. You need to get that fixed first. > > Matthew Fredrickson > > > > > Rgrds > > Markus > > > > > > Tobias Wolf wrote: > >> Hi all, > >> > >> we have used Asterisk with Standard PRI E1 Connection for some time. > >> > >> Now we have the opportunity to be connected to the PSTN over an SS7 > >> Trunk. The Device to which we will be connected is an Ericsson Axe. > >> > >> I have followed instruction from this source: > >> http://www.cesnet.cz/doc/techzpravy/2006/asterisk-ss7/ > >> > >> More precice i worked through chapter 6 to use the native ss7 capability > >> of Asterisk. > >> > >> So i downloaded, comiled and installed: > >> > >> - libss7-trunk > >> - libpri-trunk > >> - asterisk-trunk > >> > >> I have not used zaptel-trunk since the package gave a warning the it is > >> currently broken, so have have used zaptel-1.4.5.1 > >> > >> In the server is an Digium TE220B. > >> > >> Here is my zaptel configuration: > >> > >> span=1,0,0,ccs,hdb3,crc4 > >> bchan=2-31 > >> dchan=1 > >> loadzone = us > >> defaultzone=us > >> > >> B- and D-channel configuration were communicated by the owner of the > >> ericsson switch. > >> > >> Here is the zapata.conf: > >> signalling=ss7 > >> rxwink=300 > >> usecallerid=yes > >> hidecallerid=no > >> callwaiting=yes > >> usecallingpres=yes > >> callwaitingcallerid=yes > >> transfer=yes > >> canpark=yes > >> cancallforward=yes > >> callreturn=yes > >> echocancel=yes > >> echocancelwhenbridged=yes > >> rxgain=0.0 > >> txgain=0.0 > >> group=1 > >> callgroup=1 > >> pickupgroup=1 > >> immediate=no > >> ; ---------------- Options for use with signalling=ss7 ----------------- > >> ; Variant of SS7 signaling: > >> ; Options are itu and ansi > >> ss7type = itu > >> > >> ; SS7 Called Nature of Address Indicator > >> ; > >> ; unknown: Unknown > >> ; subscriber: Subscriber > >> ; national: National > >> ; international: International > >> ; dynamic: Dynamically selects the appropriate dialplan > >> ; > >> ss7_called_nai=dynamic > >> ; > >> ; SS7 Calling Nature of Address Indicator > >> ; > >> ; unknown: Unknown > >> ; subscriber: Subscriber > >> ; national: National > >> ; international: International > >> ; dynamic: Dynamically selects the appropriate dialplan > >> ; > >> ss7_calling_nai=dynamic > >> ; > >> ; > >> ; sample 1 for Germany > >> ;ss7_internationalprefix = 00 > >> ;ss7_nationalprefix = 0 > >> ;ss7_subscriberprefix = > >> ;ss7_unknownprefix = > >> ; > >> > >> ; All settings apply to linkset 1 > >> linkset = 1 > >> > >> ; Point code of the linkset. For ITU, this is the decimal number > >> ; format of the point code. For ANSI, this can either be in decimal > >> ; number format or in the xxx-xxx-xxx format > >> pointcode = 7430 > >> > >> ; Point code of node adjacent to this signaling link (Possibly the STP > >> between you and > >> ; your destination). Point code format follows the same rules as above. > >> adjpointcode = 7420 > >> > >> ; Default point code that you would like to assign to outgoing messages > >> (in case of > >> ; routing through STPs, or using A links). Point code format follows > >> the same rules > >> ; as above. > >> defaultdpc = 7420 > >> > >> ; Begin CIC (Circuit indication codes) count with this number > >> cicbeginswith = 2 > >> > >> ; What the MTP3 network indicator bits should be set to. Choices are > >> ; national, national_spare, international, international_spare > >> networkindicator=international > >> > >> ; First signaling channel > >> sigchan = 1 > >> > >> ; Channels to associate with CICs on this linkset > >> channel = 2-31 > >> > >> Here is the snippet of asterisk startup (regarding SS7): > >> -- Registered channel 2, SS7 Signalling signalling > >> -- Registered channel 3, SS7 Signalling signalling > >> -- Registered channel 4, SS7 Signalling signalling > >> -- Registered channel 5, SS7 Signalling signalling > >> -- Registered channel 6, SS7 Signalling signalling > >> -- Registered channel 7, SS7 Signalling signalling > >> -- Registered channel 8, SS7 Signalling signalling > >> -- Registered channel 9, SS7 Signalling signalling > >> -- Registered channel 10, SS7 Signalling signalling > >> -- Registered channel 11, SS7 Signalling signalling > >> -- Registered channel 12, SS7 Signalling signalling > >> -- Registered channel 13, SS7 Signalling signalling > >> -- Registered channel 14, SS7 Signalling signalling > >> -- Registered channel 15, SS7 Signalling signalling > >> -- Registered channel 16, SS7 Signalling signalling > >> -- Registered channel 17, SS7 Signalling signalling > >> -- Registered channel 18, SS7 Signalling signalling > >> -- Registered channel 19, SS7 Signalling signalling > >> -- Registered channel 20, SS7 Signalling signalling > >> -- Registered channel 21, SS7 Signalling signalling > >> -- Registered channel 22, SS7 Signalling signalling > >> -- Registered channel 23, SS7 Signalling signalling > >> -- Registered channel 24, SS7 Signalling signalling > >> -- Registered channel 25, SS7 Signalling signalling > >> -- Registered channel 26, SS7 Signalling signalling > >> -- Registered channel 27, SS7 Signalling signalling > >> -- Registered channel 28, SS7 Signalling signalling > >> -- Registered channel 29, SS7 Signalling signalling > >> -- Registered channel 30, SS7 Signalling signalling > >> -- Registered channel 31, SS7 Signalling signalling > >> -- Automatically generated pseudo channel > >> == Starting SS7 linkset on span 1 > >> == Registered channel type 'Zap' (Zapata Telephony Driver w/PRI w/SS7) > >> == Manager registered action ZapTransfer > >> == Manager registered action ZapHangup > >> == Manager registered action ZapDialOffhook > >> == Manager registered action ZapDNDon > >> == Manager registered action ZapDNDoff > >> == Manager registered action ZapShowChannels > >> == Manager registered action ZapRestart > >> chan_zap.so => (Zapata Telephony) > >> > >> > >> This is the output of ss7 debugging: > >> *CLI> ss7 debug linkset 1 > >> Enabled debugging on linkset 1 > >> *CLI> Len = 4 [ ff ff 01 03 ] > >> FSN: 127 FIB 1 > >> BSN: 127 BIB 1 > >> > >>> [0] LSSU SIOS > >>> > >> *CLI> ss7 show linkset 1 > >> SS7 linkset 1 status: Down > >> > >> *CLI> zap show channels > >> Chan Extension Context Language MOH Interpret > >> Blocked State > >> pseudo default default > >> In Service > >> 2 default default > >> Out of Ser > >> 3 default default > >> Out of Ser > >> 4 default default > >> Out of Ser > >> 5 default default > >> Out of Ser > >> 6 default default > >> Out of Ser > >> 7 default default > >> Out of Ser > >> 8 default default > >> Out of Ser > >> 9 default default > >> Out of Ser > >> 10 default default > >> Out of Ser > >> 11 default default > >> Out of Ser > >> 12 default default > >> Out of Ser > >> 13 default default > >> Out of Ser > >> 14 default default > >> Out of Ser > >> 15 default default > >> Out of Ser > >> 16 default default > >> Out of Ser > >> 17 default default > >> Out of Ser > >> 18 default default > >> Out of Ser > >> 19 default default > >> Out of Ser > >> 20 default default > >> Out of Ser > >> 21 default default > >> Out of Ser > >> 22 default default > >> Out of Ser > >> 23 default default > >> Out of Ser > >> 24 default default > >> Out of Ser > >> 25 default default > >> Out of Ser > >> 26 default default > >> Out of Ser > >> 27 default default > >> Out of Ser > >> 28 default default > >> Out of Ser > >> 29 default default > >> Out of Ser > >> 30 default default > >> Out of Ser > >> 31 default default > >> Out of Ser > >> > >> *CLI> zap show status > >> Description Alarms IRQ bpviol > >> CRC4 > >> T2XXP (PCI) Card 0 Span 1 RED 0 0 0 > >> T2XXP (PCI) Card 0 Span 2 OK 0 0 0 > >> > >> > >> Grats for anyone who has followed so far ;) > >> > >> I think it is clear that my SS7 configuration didn't work so far ... > >> My provider for SS7 connection claims that on his side everthing is up > >> and running. > >> > >> According to the information i gave above, can anybody give me a hint, > >> where to look for an error. > >> > >> I further information are required please send me an email and i will > >> try to provide them. > >> > >> Thanks in advance. > >> > >> Regards, > >> > >> > > > > > > _______________________________________________ > > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > > > asterisk-ss7 mailing list > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-ss7 > > > -- > Matthew Fredrickson > Software/Firmware Engineer > Digium, Inc. > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-ss7 mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-ss7 >
|