Hmmm.... It seems a wrong PC configuration.<br><br>The link is aligned but after sending the SLTM, it's waitng for the SLTA which never arrive.<br><br>On the remote end, they are sending an UBL message that indicate they has sent and received a correct SLTM/SLTA.
<br><br>Verify PC and SLC on both ends (chan_ss7 and Siemens side).<br><br>Robert.<br><br><br><div><span class="gmail_quote">On 5/30/07, <b class="gmail_sendername">Andrew Somov</b> <<a href="mailto:asomov12@yahoo.co.uk">
asomov12@yahoo.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Tormenta TOR3 card Asterisk chan_ss7 problem. SS7 link is flupping, Need help!!!
<br><br>I was trying to interconnect with several providers, the result was the same. The link is going up for a several seconds, then<br><br>failed with strings bellow. The channel was compiled without errors and asterisk has started with no warnings.
<br><br>Asterisk-1.2.18, chan_ss7 - 0.9 , chan_oh323, CentOS4.4 2.6.9-48.ELsmp,<br>the zaptel tor3e driver was pulled from <a href="http://www.govarion.com/tor3/">http://www.govarion.com/tor3/</a>,<br>the server is dual Intel(R) Xeon(TM) CPU
3.06GHz stepping<br>09(hyperthreading on).<br><br><br><br>This issue is quite close to<br><a href="http://lists.digium.com/pipermail/asterisk-ss7/2006-July/000410.html">http://lists.digium.com/pipermail/asterisk-ss7/2006-July/000410.html
</a><br>and<br><br><a href="http://www.asteriskguru.com/tutorials/pci_irq_apic_tdm_ticks_te410p_te405p_noise.html">http://www.asteriskguru.com/tutorials/pci_irq_apic_tdm_ticks_te410p_te405p_noise.html</a><br><br>I was explored through all and still have the same result.
<br><br><br><br>Getting this error while trying to connect to the provider (DMS switch). the ss7 link status dives:<br><br>linkset testlink, link l1, schannel 16, INSERVICE, rx: 5, tx: 3/3, sentseq/lastack: 3/3, total 33458560, 33458624
<br><br>May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:<br>Group reset still in progress for CIC=1, typ=UBL message discarded.<br><br>May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
<br>Group reset still in progress for CIC=2, typ=UBL message discarded.<br><br>May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:<br>Group reset still in progress for CIC=3, typ=UBL message discarded.<br>
<br>May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:<br>Group reset still in progress for CIC=4, typ=UBL message discarded.<br><br>May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
<br>Group reset still in progress for CIC=5, typ=UBL message discarded.<br><br>May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:<br>Group reset still in progress for CIC=6, typ=UBL message discarded.<br>
<br>May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:<br>Group reset still in progress for CIC=7, typ=UBL message discarded.<br>etc. (cut)<br><br>May 30 16:48:15 WARNING[12951]: mtp.c:791 timeout_sltm_t1: No SLTA received within
Q.707 timer T1, trying again on link 'l1'.<br><br>May 30 16:48:24 ERROR[12951]: mtp.c:796 timeout_sltm_t1: No SLTA received within Q.707 timer T1, faulting link on link 'l1'.<br><br>May 30 16:48:24 WARNING[12951]: chan_ss7.c:636 monitor_main: MTP is now DOWN on link 'l1'.
<br><br>May 30 16:48:24 NOTICE[12951]: mtp.c:502 mtp_changeover: MTP changeover<br>last_ack=3, last_sent=3, from schannel 16, no INSERVICE schannel found<br><br>May 30 16:48:24 NOTICE[12951]: mtp.c:506 mtp_changeover: Failover not
<br>possible, no other signalling link and no other host available.<br><br>testlink*CLI> ss7 link status<br><br>linkset testlink, link l1, schannel 16, DOWN, rx: 2, tx: 4/4, sentseq/lastack: 3/4, total 33467808, 33467872
<br><br>testlink*CLI> ss7 link status<br><br>linkset testlink, link l1, schannel 16, NOT_ALIGNED, rx: 0, tx: 1/4, sentseq/lastack: 127/127, total 35673520, 35673584<br><br>May 30 16:49:40 WARNING[12951]: mtp.c:424 t2_timeout: MTP2 timer T2
<br>timeout (failed to receive 'O', 'N', or 'E' after sending 'O'), initial<br>alignment failed on link 'l1'.<br><br><br><br>My /etc/asterisk/zapata.conf is empty,<br><br>cat /etc/zaptel.conf gives
<br><br>span=1,1,0,ccs,hdb3<br><br>bchan=1-31<br><br>span=2,2,0,ccs,hdb3<br><br>bchan=32-62<br><br>span=3,3,0,ccs,hdb3<br><br>bchan=63-93<br><br>span=4,4,0,ccs,hdb3<br><br>bchan=94-124<br><br>loadzone = uk<br><br>defaultzone = uk
<br><br><br><br>cat /etc/asterisk/ss7.conf :<br><br><br><br>[linkset-testlink]<br><br>enabled => yes<br><br>enable_st => no<br><br>use_connect => no<br><br>hunting_policy => even_mru<br><br>;t35 => 15000,timeout
<br><br>subservice => 8<br><br>context => default<br><br>language => en<br><br><br><br>[link-l1]<br><br>linkset => testlink<br><br>enabled => yes<br><br>channels => 1-15,17-31<br><br>schannel => 16<br>
<br>firstcic => 1<br><br><br><br>[link-l2]<br><br>linkset => testlink<br><br>enabled => yes<br><br>channels => 1-15,17-31<br><br>schannel =><br><br>firstcic => 33<br><br><br><br>[link-l3]<br><br>enabled => yes
<br><br>linkset => testlink<br><br>channels => 1-15,17-31<br><br>schannel =><br><br>firstcic => 65<br><br><br><br>[link-l4]<br><br>enabled => no<br><br>linkset => testlink<br><br>channels => 1-15,17-31
<br><br>schannel =><br><br>firstcic => 97<br><br><br><br>[<a href="http://host-host.domain.com">host-host.domain.com</a>]<br><br>enabled => yes<br><br>default_linkset => testlink<br><br>;autopc => yes<br><br>
opc => 0x27f2 ;13131<br><br>dpc => testlink:0x3b48 ;->provider1 (0x334b ;-> provider2)<br><br>if-1 => my.host.ip.addr<br><br>links => l1:1,l2:2,l3:3,l4:4<br><br><br><br>/sbin/lsmod<br><br>Module Size Used by
<br><br>zttranscode 12552 0<br><br>tor3e 89116 0<br><br>zaptel 186532 184 zttranscode,tor3e<br><br>crc_ccitt 6209 1 zaptel<br><br>md5 8129 1
<br><br>ipv6 243425 30<br><br>autofs4 25413 0<br><br>sunrpc 143909 1<br><br>button 10705 0<br><br>battery 12997 0<br><br>ac 8901 0
<br><br>hw_random 9685 0<br><br>e1000 119249 0<br><br>floppy 58193 0<br><br>ata_piix 19141 0<br><br>libata 105757 1 ata_piix<br><br>sg 38369 0
<br><br>dm_snapshot 21093 0<br><br>dm_zero 6337 0<br><br>dm_mirror 31173 0<br><br>ext3 119113 2<br><br>jbd 59609 1 ext3<br><br>dm_mod 64617 8 dm_snapshot,dm_zero,dm_mirror
<br><br>aic79xx 187613 5<br><br>sd_mod 20545 9<br><br>scsi_mod 119757 4 libata,sg,aic79xx,sd_mod<br><br><br><br>cat /proc/interrupts gives shows that tor3e IRQ 217 is in the different CPU from the eth0 network card:
<br><br><br><br> CPU0 CPU1 CPU2 CPU3<br><br> 0: 2981832 2911004 2910992 2904442 IO-APIC-edge timer<br><br> 1: 8 69 50 0 IO-APIC-edge i8042
<br><br> 8: 1 0 0 0 IO-APIC-edge rtc<br><br> 9: 9 0 0 0 IO-APIC-level acpi<br><br>185: 30 0 0 0 IO-APIC-level aic79xx
<br><br>193: 4999 1944 3374 8368 IO-APIC-level aic79xx<br><br>201: 52790 0 0 0 IO-APIC-level eth0<br><br>217: 0 5284112 5280614 20005 IO-APIC-level tor3e
<br><br>NMI: 0 0 0 0<br><br>LOC: 11708215 11708091 11708090 11708212<br><br>ERR: 0<br><br>MIS: 0<br><br><br><br>#lspci -vb gives me the output bellow. (On IRQ 9 there are olso RAID bus, ethernet, and I mentioned there is no latency)
<br><br>#lspci -v gives IRQ 217, proved that APIC is running and it is unique.<br><br>03:0a.0 Bridge: PLX Technology, Inc.: Unknown device d44d (rev 01)<br><br> Subsystem: PLX Technology, Inc.: Unknown device 9030<br>
<br> Flags: medium devsel, IRQ 9<br><br> Memory at fe6f0000 (32-bit, non-prefetchable)<br><br> I/O ports at 2000<br><br> Memory at fe6e0000 (32-bit, non-prefetchable)<br><br> Memory at fe6d0000 (32-bit, non-prefetchable)
<br><br> Capabilities: [40] Power Management version 1<br><br> Capabilities: [48] #06 [0000]<br><br> Capabilities: [4c] Vital Product Data<br><br><br><br>#dmesg output shows:<br><br>ACPI: PCI Interrupt 0000:03:
0a.0[A] -> GSI 28 (level, low) -> IRQ 217<br><br>Detected Tormenta 3 Quad E1 - TOR3 at 0xfe6e0000/0xfe6d0000 irq 217<br><br>Xilinx Chip successfully loaded, configured and started!!<br><br>Detected Card number: 0<br>
<br>Tor3: Launching card: 0<br><br>Registered Tormenta 3-E PCI<br><br>Registered tone zone 4 (United Kingdom)<br><br>SPAN 1: Primary Sync Source<br><br>SPAN 2: Secondary Sync Source<br><br>SPAN 3: Tertiary Sync Source<br>
<br>SPAN 4: Quaternary Sync Source<br><br>Zapata Telephony Interface Registered on major 196<br><br>Zaptel Version: <a href="http://1.2.17.1">1.2.17.1</a><br><br>Zaptel Echo Canceller: KB1<br><br>Zaptel: Master changed to Tor3/0/2
<br><br>Zaptel: Master changed to Tor3/0/3<br><br>Zaptel: Master changed to Tor3/0/4<br><br>Zaptel: Master changed to Tor3/0/1<br><br>Zaptel Transcoder support loaded<br><br><br><br>So, my question is: is it possible to make a chan_ss7 work with
<br>Govarion Tormenta 3 cards at all? Or shell I migrate to the native<br>asterisk SS7? I'll appreciate any help.<br><br><br><br><br>___________________________________________________________<br>Inbox full of unwanted email? Get leading protection and 1GB storage with All New Yahoo! Mail.
<a href="http://uk.docs.yahoo.com/nowyoucan.html">http://uk.docs.yahoo.com/nowyoucan.html</a><br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com
</a> --<br><br>asterisk-ss7 mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-ss7">http://lists.digium.com/mailman/listinfo/asterisk-ss7</a><br></blockquote>
</div><br>