Hi Attila I had the mtp2 setup and not hardhdlc. Im using sangoma 3.5.4.17. I think it also crush the system as I tried to put the crossover cable and the system constantly reboot. I will try 3.4.1 shortly and revert Sam -------------- Hi, the problem is: hardhdlc=16 replace to mtp2=16 hint: don't try wanpipe 3.4.4 this cause kernel panic with mtp2 wanpipe-3.4.1 + dahdi 2.1.0.4 works fine here Regards, Attila On Mon, 2009-08-03 at 00:38 -0500, research at businesstz.com wrote: > Hi Alejendro > > Have you managed to find out the solution to your problem!! Im facing the > same problem. The same link connects on another digium card running in > parallel with exactly the same configuration. > > Please share with me if you have a clue as I want to try sangoma..i'm > using A104DE instead > > Kind regards > Sam > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 4 Jun 2009 11:29:15 -0600 > From: Alejandro Mej?a Evertsz <amejia at carmeltelecom.com> > Subject: [asterisk-ss7] Sangoma A102 + Dahdi + libss7 + Asterisk - > Linkset DOWN > To: <asterisk-ss7 at lists.digium.com> > Message-ID: <006501c9e539$fd815d20$f8841760$@com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > > > I have problems, as linkset shows as DOWN all the time with the following > scenario: > > > > -Dell server with Sangoma A102 (2 E1/T1 Card) > > -Ubuntu Server 8.10 > > -Dahdi Linux 2.1.0.4 > > -libss7 1.0.2 > > -wanpipe 3.4.1 > > -Asterisk 1.6.1.0 > > > > ===/etc/dahdi/system.conf=== > > loadzone=us > > defaultzone=us > > > > #Sangoma A102 port 1 [slot:2 bus:10 span:1] <wanpipe1> > > span=1,0,0,ccs,hdb3 > > bchan=1-15,17-31 > > echocanceller=mg2,1-15,17-31 > > hardhdlc=16 > > > > #Sangoma A102 port 2 [slot:2 bus:10 span:2] <wanpipe2> > > span=2,1,0,ccs,hdb3 > > bchan=32-46,48-62 > > echocanceller=mg2,32-46,48-62 > > hardhdlc=47 > > =======END============== > > > > ===/etc/asterisk/chan_dahdi.conf=== > > [trunkgroups] > > > > [channels] > > context=default > > usecallerid=yes > > hidecallerid=no > > callwaiting=yes > > usecallingpres=yes > > callwaitingcallerid=yes > > threewaycalling=yes > > transfer=yes > > canpark=yes > > cancallforward=yes > > callreturn=yes > > echocancel=yes > > echocancelwhenbridged=yes > > relaxdtmf=yes > > rxgain=0.0 > > txgain=0.0 > > group=1 > > callgroup=1 > > pickupgroup=1 > > immediate=no > > > > ;Sangoma A102 port 1 [slot:2 bus:10 span:1] <wanpipe1> > > context=from-pstn > > group=0 > > echocancel=yes > > ;switchtype=euroisdn > > signalling=ss7 > > ss7type=itu > > linkset = 1 > > pointcode = 1234 > > adjpointcode = 4321 > > defaultdpc = 4132 > > cicbeginswith = 1 > > networkindicator=national > > sigchan = 16 > > ;sigchannel = 16 > > channel => 1-15,17-31 > > > > ;Sangoma A102 port 2 [slot:2 bus:10 span:2] <wanpipe2> > > context=from-pstn > > group=1 > > echocancel=yes > > ;switchtype=euroisdn > > signalling=ss7 > > ss7type=itu > > linkset = 2 > > pointcode = 4321 > > adjpointcode = 1234 > > defaultdpc = 4132 > > cicbeginswith = 32 > > networkindicator=national > > sigchan = 47 > > ;sigchannel = 47 > > channel => 32-46,48-62 > > =============END========================= > > > > As I don?t have an SS7 equipment/link to test, I decided to make a crossover > cable (1<-->4, 2<-->5) and plugged port 1 to port 2 on the same card. > > Everything seems to come up correctly, but when I do: ?ss7 show linkset 1? > it shows as down > > > > *CLI> ss7 show linkset 1 > > SS7 linkset 1 status: Down > > > > Even if links on the card, and dahdi status seems ok: > > > > *CLI> dahdi show status > > Description Alarms IRQ bpviol CRC4 Fra > Codi Options LBO > > wanpipe1 card 0 OK 0 0 0 CCS > HDB3 YEL 0 db (CSU)/0-133 feet (DSX-1) > > wanpipe2 card 1 OK 0 0 0 CCS > HDB3 YEL 0 db (CSU)/0-133 feet (DSX-1) > > > > When using ss7linktest I get this: > > > > # /usr/src/libss7-1.0.2/ss7linktest 16 itu 1234 4321 > > Starting link 1 > > Link state change: IDLE -> NOTALIGNED > > Len = 4 [ ff ff 01 00 ] > > FSN: 127 FIB 1 > > BSN: 127 BIB 1 > > >[0] LSSU SIO > > > > I have no experience at all using ss7 (I only have used ISDN PRI), so please > be patient if you find I?m doing something totally wrong hehehe. > > > > Thanks in advance for your help! > > > > Regards, > > > > Alejandro Mej?a > > > > > > _______________________________________________ > --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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.digium.com/pipermail/asterisk-ss7/attachments/20090803/ba26c794 /attachment-0001.pgp ------------------------------ _______________________________________________ --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 54, Issue 3 ******************************************* No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.38/2274 - Release Date: 08/02/09 17:56:00
|