Hi, use sltm=>no on the link side. Good luck --- En date de?: Lun 29.9.08, asterisk-ss7-request at lists.digium.com <asterisk-ss7-request at lists.digium.com> a ?crit?: > De: asterisk-ss7-request at lists.digium.com <asterisk-ss7-request at lists.digium.com> > Objet: asterisk-ss7 Digest, Vol 43, Issue 35 > ?: asterisk-ss7 at lists.digium.com > Date: Lundi 29 Septembre 2008, 19h00 > Send asterisk-ss7 mailing list submissions to > asterisk-ss7 at lists.digium.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.digium.com/mailman/listinfo/asterisk-ss7 > or, via email, send a message with subject or body > 'help' to > asterisk-ss7-request at lists.digium.com > > You can reach the person managing the list at > asterisk-ss7-owner at lists.digium.com > > When replying, please edit your Subject line so it is more > specific > than "Re: Contents of asterisk-ss7 digest..." > > > Today's Topics: > > 1. Does Sangoma 101 Card work on libss7 (mark morreny) > 2. Re: Does Sangoma 101 Card work on libss7 (Anton) > 3. Re: Does Sangoma 101 Card work on libss7 (Krzysztof > Drewicz) > 4. chan_ss7, sangoma A104 to local telecom partner, but > NOT_ALIGNED, MTP send fifo not ready, BLOCKED Local > Hardware > (Robert Verspuy) > 5. Re: chan_ss7, sangoma A104 to local telecom > partner, but > NOT_ALIGNED, MTP send fifo not ready, BLOCKED Local > Hardware > (Kristian Nielsen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 29 Sep 2008 09:59:36 +0800 > From: "mark morreny" > <markmorreny at gmail.com> > Subject: [asterisk-ss7] Does Sangoma 101 Card work on > libss7 > To: asterisk-ss7 at lists.digium.com > Message-ID: > <20ad6b920809281859v1ee8759eq5ea20efe344f0247 at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > I have two Sangoma 101 cards that I would like to use to > hook up two > Asterisk. I tried with Asterisk 1.6 and libss7 but I > can't get it to work. > > Does anyone know how to get it to work? I would greatly > appreciate it if > someone can share with me the config. > > Any help will be wonderful. > > Thanks in advance for your kindness. > > Mark > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.digium.com/pipermail/asterisk-ss7/attachments/20080929/b3361ca3/attachment-0001.htm > > > ------------------------------ > > Message: 2 > Date: Mon, 29 Sep 2008 12:02:06 +0500 > From: Anton <anton.vazir at gmail.com> > Subject: Re: [asterisk-ss7] Does Sangoma 101 Card work on > libss7 > To: asterisk-ss7 at lists.digium.com > Message-ID: > <200809291202.06117.anton.vazir at gmail.com> > Content-Type: text/plain; charset="iso-8859-6" > > As for DAHDI support, Sangoma should have it's support > in > the latest beta drivers. I did not try myself though, just > got this info recently. > > On Monday 29 September 2008 06:59, mark morreny wrote: > > Hi, > > > > I have two Sangoma 101 cards that I would like to use > to > > hook up two Asterisk. I tried with Asterisk 1.6 and > > libss7 but I can't get it to work. > > > > Does anyone know how to get it to work? I would > greatly > > appreciate it if someone can share with me the config. > > > > Any help will be wonderful. > > > > Thanks in advance for your kindness. > > > > Mark > > > > ------------------------------ > > Message: 3 > Date: Mon, 29 Sep 2008 09:14:23 +0200 > From: "Krzysztof Drewicz" > <krzysztofdrewicz at gmail.com> > Subject: Re: [asterisk-ss7] Does Sangoma 101 Card work on > libss7 > To: asterisk-ss7 at lists.digium.com > Message-ID: > <9372a8330809290014y2e378068wae7d774db99f1f83 at mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > 2008/9/29 Anton <anton.vazir at gmail.com>: > > As for DAHDI support, Sangoma should have it's > support in > > the latest beta drivers. I did not try myself though, > just > > got this info recently. > > Just turn off the hardhdlc, and put dchan in zapata/dahdi. > Works for me. > > > > -- > Krzysztof Drewicz > +48 504 17 55 77 > > > > ------------------------------ > > Message: 4 > Date: Mon, 29 Sep 2008 11:59:32 +0200 > From: Robert Verspuy <robert at exa-omicron.nl> > Subject: [asterisk-ss7] chan_ss7, sangoma A104 to local > telecom > partner, but NOT_ALIGNED, MTP send fifo not ready, BLOCKED > Local > Hardware > To: asterisk-ss7 at lists.digium.com > Message-ID: <48E0A704.70502 at exa-omicron.nl> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > All, > > I'm trying to setup 2 SS7 links from one asterisk > switch to out local > telecom partner. > I've installed libpri 1.4.7, zaptel 1.4.12, wanpipe > 3.2.7.1, asterisk > 1.4.21.2 and chan_ss7 1.0.95-beta > > I have two links, with both different peer endcodes. > The wanrouter status gives me the status connected. (ignore > port 3, it > will be used for a ISDN-30 line when ss7 is working) > When I freshly start Asterisk, I see the status > "INSERVICE" for both > links, but that switch to DOWN and NOT_ALIGNED within a few > seconds, > with a few warnings. > > calcium*CLI> ss7 link status > linkset Rt, link a, schannel 16, sls 0, INSERVICE, rx: 3, > tx: 3/3, > sentseq/lastack: 3/3, total 55408, 55504 > linkset Ut, link b, schannel 16, sls 0, INSERVICE, rx: 4, > tx: 3/3, > sentseq/lastack: 3/3, total 55408, 55504 > [Sep 29 11:24:21] WARNING[2330]: mtp.c:940 timeout_sltm_t1: > No SLTA > received within Q.707 timer T1, trying again on link > 'a'. > [Sep 29 11:24:21] WARNING[2330]: mtp.c:940 timeout_sltm_t1: > No SLTA > received within Q.707 timer T1, trying again on link > 'b'. > [Sep 29 11:24:24] NOTICE[2330]: mtp.c:1040 > mtp2_process_lssu: Got status > indication 'OS' while INSERVICE on link > 'a'. > [Sep 29 11:24:24] WARNING[2330]: chan_ss7.c:622 > process_event: MTP is > now DOWN on link 'a'. > [Sep 29 11:24:24] NOTICE[2330]: mtp.c:593 mtp_changeover: > MTP changeover > last_ack=4, last_sent=4, from schannel 16, no INSERVICE > schannel found > [Sep 29 11:24:24] NOTICE[2330]: mtp.c:597 mtp_changeover: > Failover not > possible, no other signalling link and no other host > available. > [Sep 29 11:24:24] NOTICE[2330]: mtp.c:1040 > mtp2_process_lssu: Got status > indication 'OS' while INSERVICE on link > 'b'. > [Sep 29 11:24:24] WARNING[2330]: chan_ss7.c:622 > process_event: MTP is > now DOWN on link 'b'. > [Sep 29 11:24:24] NOTICE[2330]: mtp.c:593 mtp_changeover: > MTP changeover > last_ack=4, last_sent=4, from schannel 16, no INSERVICE > schannel found > [Sep 29 11:24:24] NOTICE[2330]: mtp.c:597 mtp_changeover: > Failover not > possible, no other signalling link and no other host > available. > calcium*CLI> ss7 link status > linkset Rt, link a, schannel 16, sls 0, NOT_ALIGNED, rx: 1, > tx: 3/4, > sentseq/lastack: 127/127, total 137040, 137136 > linkset Ut, link b, schannel 16, sls 0, NOT_ALIGNED, rx: 1, > tx: 3/4, > sentseq/lastack: 127/127, total 137040, 137136 > > After that all links have the status "Idle Reset > pending BLOCKED Local > Hardware". > > Several other warning I have after running "ss7 > reset" > [Sep 29 11:25:17] WARNING[2349]: l4isup.c:396 > mtp_enqueue_isup_packet: > MTP send fifo not ready. > [Sep 29 11:25:41] WARNING[2330]: mtp.c:470 t2_timeout: MTP2 > timer T2 > timeout (failed to receive 'O', 'N', or > 'E' after sending 'O'), initial > alignment failed on link 'a'. > [Sep 29 11:25:41] WARNING[2330]: mtp.c:470 t2_timeout: MTP2 > timer T2 > timeout (failed to receive 'O', 'N', or > 'E' after sending 'O'), initial > alignment failed on link 'b'. > [Sep 29 11:25:47] NOTICE[2330]: l4isup.c:1236 t22_timeout: > T22 timeout > (No "circuit group reset acknowledge" from peer) > CIC=1. > [Sep 29 11:25:47] WARNING[2330]: l4isup.c:396 > mtp_enqueue_isup_packet: > MTP send fifo not ready. > [Sep 29 11:25:47] NOTICE[2330]: l4isup.c:1236 t22_timeout: > T22 timeout > (No "circuit group reset acknowledge" from peer) > CIC=17. > [Sep 29 11:25:47] WARNING[2330]: l4isup.c:396 > mtp_enqueue_isup_packet: > MTP send fifo not ready. > > Does anyone have any idea where to start searching, or > troubleshooting? > Is it possible that the wanpipe drivers are not compiled > correctly? > (you've got a lot of options there). > Should I also get the mtp3 daemon running? Can't find > any information > about when this mtp3 daemon is necessary. > > The only information the local telco could provide was: > Networkindicator=3 > slc=0 > > I asume the networkindicator is something like the > subservice in the > ss7.conf file? > But I don't know what the slc value is.. > > Thnx in advance! > > Regards, > Robert Verspuy > > == wanrouter status == > > [root at calcium etc]# /etc/init.d/wanrouter status > > > > Devices currently active: > > wanpipe1 wanpipe2 wanpipe3 > > > > > > Wanpipe Config: > > > > Device name | Protocol Map | Adapter | IRQ | Slot/IO > | If's | CLK | > > Baud rate | > > wanpipe1 | N/A | A101/1D/A102/2D/4/4D/8| > 169 | 4 | > > 1 | EXT | 0 | > > wanpipe2 | N/A | A101/1D/A102/2D/4/4D/8| > 169 | 4 | > > 1 | EXT | 0 | > > wanpipe3 | N/A | A101/1D/A102/2D/4/4D/8| > 169 | 4 | > > 1 | EXT | 0 | > > > > Wanrouter Status: > > > > Device name | Protocol | Station | Status | > > wanpipe1 | AFT HDLC | N/A | Connected | > > wanpipe2 | AFT HDLC | N/A | Connected | > > wanpipe3 | AFT HDLC | N/A | Connecting | > == wanrouter status == > > == /etc/zaptel.conf == > > loadzone=nl > > defaultzone=nl > > > > #Sangoma A104 port 1 [slot:4 bus:8 span:1] > <wanpipe1> > > span=1,0,0,ccs,hdb3 > > bchan=1-31 > > #Sangoma A104 port 2 [slot:4 bus:8 span:2] > <wanpipe2> > > span=2,0,0,ccs,hdb3 > > bchan=32-62 > > > > #Sangoma A104 port 3 [slot:4 bus:8 span:3] > <wanpipe3> > > span=3,0,0,ccs,hdb3 > > bchan=63-77,79-93 > > hardhdlc=78 > == /etc/zaptel.conf == > > == /etc/wanpipe1.conf == > > [devices] > > wanpipe1 = WAN_AFT_TE1, Comment > > > > [interfaces] > > w1g1 = wanpipe1, , TDM_VOICE, Comment > > > > [wanpipe1] > > CARD_TYPE = AFT > > S514CPU = A > > CommPort = PRI > > AUTO_PCISLOT = NO > > PCISLOT = 4 > > PCIBUS = 8 > > FE_MEDIA = E1 > > FE_LCODE = HDB3 > > FE_FRAME = NCRC4 > > FE_LINE = 1 > > TE_CLOCK = NORMAL > > TE_REF_CLOCK = 0 > > TE_SIG_MODE = CCS > > TE_HIGHIMPEDANCE = NO > > LBO = 120OH > > FE_TXTRISTATE = NO > > MTU = 1500 > > UDPPORT = 9000 > > TTL = 255 > > IGNORE_FRONT_END = NO > > TDMV_SPAN = 1 > > TDMV_DCHAN = 16 > > TDMV_HW_DTMF = NO > > > > [w1g1] > > ACTIVE_CH = ALL > > TDMV_ECHO_OFF = NO > > TDMV_HWEC = YES > == /etc/wanpipe1.conf == > > == /etc/wanpipe2.conf == > > > > [devices] > > wanpipe2 = WAN_AFT_TE1, Comment > > > > [interfaces] > > w2g1 = wanpipe2, , TDM_VOICE, Comment > > > > [wanpipe2] > > CARD_TYPE = AFT > > S514CPU = A > > CommPort = PRI > > AUTO_PCISLOT = NO > > PCISLOT = 4 > > PCIBUS = 8 > > FE_MEDIA = E1 > > FE_LCODE = HDB3 > > FE_FRAME = NCRC4 > > FE_LINE = 2 > > TE_CLOCK = NORMAL > > TE_REF_CLOCK = 0 > > TE_SIG_MODE = CCS > > TE_HIGHIMPEDANCE = NO > > LBO = 120OH > > FE_TXTRISTATE = NO > > MTU = 1500 > > UDPPORT = 9000 > > TTL = 255 > > IGNORE_FRONT_END = NO > > TDMV_SPAN = 2 > > TDMV_DCHAN = 16 > > TDMV_HW_DTMF = NO > > > > [w2g1] > > ACTIVE_CH = ALL > > TDMV_ECHO_OFF = NO > > TDMV_HWEC = YES > == /etc/wanpipe2.conf == > > == /etc/asterisk/ss7.conf == > > [linkset-Rt] > > enabled => yes ; The > linkset is enabled > > enable_st => no ; The > end-of-pulsing (ST) is > > not used to determine when incoming address is > complete > > use_connect => yes ; Reply > incoming call with CON > > rather than ACM and ANM > > hunting_policy => even_mru ; The CIC > hunting policy > > (even_mru, odd_lru, seq_lth, seq_htl) is even CIC > numbers, most > > recently used > > context => from-ss7 ; Incoming calls are > placed in the ss7 > > context in the asterisk dialplan > > language => nl ; The > language for this > > context is da > > subservice => 3 ; The > subservice field: > > national (8), international (0), auto or decimal/hex > value > > ; The auto > means that the > > subservice is obtained from first received SLTM > > > > [linkset-Ut] > > enabled => yes ; The > linkset is enabled > > enable_st => no ; The > end-of-pulsing (ST) is > > not used to determine when incoming address is > complete > > use_connect => yes ; Reply > incoming call with CON > > rather than ACM and ANM > > hunting_policy => even_mru ; The CIC > hunting policy > > (even_mru, odd_lru, seq_lth, seq_htl) is even CIC > numbers, most > > recently used > > context => from-ss7 ; Incoming calls are > placed in the ss7 > > context in the asterisk dialplan > > language => nl ; The > language for this > > context is da > > subservice => 3 ; The > subservice field: > > national (8), international (0), auto or decimal/hex > value > > ; The auto > means that the > > subservice is obtained from first received SLTM > > > > [link-a] > > enabled => yes ; The link > is enabled > > linkset => Rt ; This link > belongs to linkset siuc > > channels => 1-15,17-31 ; The > speech/audio circuit > > channels on this link > > schannel => 16 ; The > signalling channel > > firstcic => 1 ; The first > CIC > > > > [link-b] > > enabled => yes ; The link > is enabled > > linkset => Ut ; This link > belongs to linkset siuc > > channels => 1-15,17-31 ; The > speech/audio circuit > > channels on this link > > schannel => 16 ; The > signalling channel > > firstcic => 1 ; The first > CIC > > > > [host-calcium] > > enabled => yes ; The host > is enabled > > opc => 12 ; The point > code for this SS7 > > signalling point is 0x8e0 > > dpc => Rt:34,Ut:56 ; The destination > point (peer) code is > > 0x3fff for linkset siuc > > links => a:1,b:2 ; Syntax: links > => > > link-name:digium-connector-no > > ; The links on > the host is > > 'l1', connected to span/connector #1 > > if-1=127.0.0.1 > > default_linkset => Rt > == /etc/asterisk/ss7.conf == > > > -- > *Exa-Omicron* > Patroonsweg 10 > 3892 DB Zeewolde > Tel.: 088-OMICRON (66 427 66) > http://www.exa-omicron.nl > > > > ------------------------------ > > Message: 5 > Date: Mon, 29 Sep 2008 12:26:53 +0200 > From: Kristian Nielsen <knmeister at gmail.com> > Subject: Re: [asterisk-ss7] chan_ss7, sangoma A104 to local > telecom > partner, but NOT_ALIGNED, MTP send fifo not ready, BLOCKED > Local > Hardware > To: asterisk-ss7 at lists.digium.com > Message-ID: <87vdwf9riq.fsf at gmail.com> > Content-Type: text/plain; charset=us-ascii > > Robert Verspuy <robert at exa-omicron.nl> writes: > > > [Sep 29 11:24:21] WARNING[2330]: mtp.c:940 > timeout_sltm_t1: No SLTA > > received within Q.707 timer T1, trying again on link > 'a'. > > This has been covered in several threads in the past, you > might want to check > the archives. > > In short, the other end is not properly doing the SLTR/SLTA > part of > SS7. Either disable slta checking on your end, or get the > other end to enable > it. > > - Kristian. > > > > ------------------------------ > > _______________________________________________ > --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 > > End of asterisk-ss7 Digest, Vol 43, Issue 35 > ********************************************
![]() |