[asterisk-ss7] Re: asterisk-ss7 Digest, Vol 27, Issue 16
Matthew Fredrickson
creslin at digium.com
Thu May 31 10:55:42 MST 2007
On May 31, 2007, at 11:28 AM, Andrew Somov wrote:
> Hi, the problem is gone and everything is working well and stable as
> soon as I changed an opc and dpc into decimal format.
> And I think the zttranscode is in use by chan_zap for codecs
> transcoding:
zttranscode is used by codec_zap.so for transcoding.
Matthew Fredrickson
>
> CLI>ss7 version
> chan_ss7 version 0.9+ss7.pl+autopc
>
> /sbin/lsmod
> Module Size Used by
> zttranscode 12552 0
> tor3e 89116 0
> zaptel 186532 184 zttranscode,tor3e
> crc_ccitt 6209 1 zaptel
>
> Thank you All
>
> ----- Original Message ----
> From: "asterisk-ss7-request at lists.digium.com"
> <asterisk-ss7-request at lists.digium.com>
> To: asterisk-ss7 at lists.digium.com
> Sent: Thursday, 31 May, 2007 3:13:21 PM
> Subject: asterisk-ss7 Digest, Vol 27, Issue 16
>
> 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. RES: asterisk-ss7 Digest, Vol 27, Issue 15
> (Virmones P.T de Miranda)
> 2. Core dump in chan_ss7 -- here's the backtrace
> (Juan Carlos Castro y Castro)
> 3. Re: Core dump in chan_ss7 -- here's the backtrace (Robert Kenton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 30 May 2007 20:26:39 -0300
> From: "Virmones P.T de Miranda" <virmones.tavares at govoip.com.br>
> Subject: [asterisk-ss7] RES: asterisk-ss7 Digest, Vol 27, Issue 15
> To: <asterisk-ss7 at lists.digium.com>
> Message-ID: <001301c7a311$faab2480$0401010a at FOMICIANOGOVOIP>
> Content-Type: text/plain; charset="us-ascii"
>
> Iam solve this problem, after 2 days just using:
> rmmod zttranscode
>
>
>
>
> -----Mensagem original-----
> De: asterisk-ss7-bounces at lists.digium.com
> [mailto:asterisk-ss7-bounces at lists.digium.com] Em nome de
> asterisk-ss7-request at lists.digium.com
> Enviada em: quarta-feira, 30 de maio de 2007 19:19
> Para: asterisk-ss7 at lists.digium.com
> Assunto: asterisk-ss7 Digest, Vol 27, Issue 15
>
> 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. Tormenta TOR3 card Asterisk chan_ss7 (Andrew Somov)
> 2. Re: Tormenta TOR3 card Asterisk chan_ss7 (Robert Kenton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 30 May 2007 20:21:49 +0000 (GMT)
> From: Andrew Somov <asomov12 at yahoo.co.uk>
> Subject: [asterisk-ss7] Tormenta TOR3 card Asterisk chan_ss7
> To: asterisk-ss7 at lists.digium.com
> Message-ID: <240724.13787.qm at web26603.mail.ukl.yahoo.com>
> Content-Type: text/plain; charset=ascii
>
> Tormenta TOR3 card Asterisk chan_ss7 problem. SS7 link is flupping,
> Need
> help!!!
>
> I was trying to interconnect with several providers, the result was the
> same. The link is going up for a several seconds, then
>
> failed with strings bellow. The channel was compiled without errors and
> asterisk has started with no warnings.
>
> Asterisk-1.2.18, chan_ss7 - 0.9 , chan_oh323, CentOS4.4 2.6.9-48.ELsmp,
> the zaptel tor3e driver was pulled from http://www.govarion.com/tor3/,
> the server is dual Intel(R) Xeon(TM) CPU 3.06GHz stepping
> 09(hyperthreading on).
>
>
>
> This issue is quite close to
> http://lists.digium.com/pipermail/asterisk-ss7/2006-July/000410.html
> and
>
> http://www.asteriskguru.com/tutorials/
> pci_irq_apic_tdm_ticks_te410p_te405p_n
> oise.html
>
> I was explored through all and still have the same result.
>
>
>
> Getting this error while trying to connect to the provider (DMS
> switch). the
> ss7 link status dives:
>
> linkset testlink, link l1, schannel 16, INSERVICE, rx: 5, tx: 3/3,
> sentseq/lastack: 3/3, total 33458560, 33458624
>
> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
> Group reset still in progress for CIC=1, typ=UBL message discarded.
>
> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
> Group reset still in progress for CIC=2, typ=UBL message discarded.
>
> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
> Group reset still in progress for CIC=3, typ=UBL message discarded.
>
> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
> Group reset still in progress for CIC=4, typ=UBL message discarded.
>
> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
> Group reset still in progress for CIC=5, typ=UBL message discarded.
>
> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
> Group reset still in progress for CIC=6, typ=UBL message discarded.
>
> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
> Group reset still in progress for CIC=7, typ=UBL message discarded.
> etc. (cut)
>
> 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'.
>
> 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'.
>
> May 30 16:48:24 WARNING[12951]: chan_ss7.c:636 monitor_main: MTP is
> now DOWN
> on link 'l1'.
>
> May 30 16:48:24 NOTICE[12951]: mtp.c:502 mtp_changeover: MTP changeover
> last_ack=3, last_sent=3, from schannel 16, no INSERVICE schannel found
>
> May 30 16:48:24 NOTICE[12951]: mtp.c:506 mtp_changeover: Failover not
> possible, no other signalling link and no other host available.
>
> testlink*CLI> ss7 link status
>
> linkset testlink, link l1, schannel 16, DOWN, rx: 2, tx: 4/4,
> sentseq/lastack: 3/4, total 33467808, 33467872
>
> testlink*CLI> ss7 link status
>
> linkset testlink, link l1, schannel 16, NOT_ALIGNED, rx: 0, tx: 1/4,
> sentseq/lastack: 127/127, total 35673520, 35673584
>
> May 30 16:49:40 WARNING[12951]: mtp.c:424 t2_timeout: MTP2 timer T2
> timeout (failed to receive 'O', 'N', or 'E' after sending 'O'), initial
> alignment failed on link 'l1'.
>
>
>
> My /etc/asterisk/zapata.conf is empty,
>
> cat /etc/zaptel.conf gives
>
> span=1,1,0,ccs,hdb3
>
> bchan=1-31
>
> span=2,2,0,ccs,hdb3
>
> bchan=32-62
>
> span=3,3,0,ccs,hdb3
>
> bchan=63-93
>
> span=4,4,0,ccs,hdb3
>
> bchan=94-124
>
> loadzone = uk
>
> defaultzone = uk
>
>
>
> cat /etc/asterisk/ss7.conf :
>
>
>
> [linkset-testlink]
>
> enabled => yes
>
> enable_st => no
>
> use_connect => no
>
> hunting_policy => even_mru
>
> ;t35 => 15000,timeout
>
> subservice => 8
>
> context => default
>
> language => en
>
>
>
> [link-l1]
>
> linkset => testlink
>
> enabled => yes
>
> channels => 1-15,17-31
>
> schannel => 16
>
> firstcic => 1
>
>
>
> [link-l2]
>
> linkset => testlink
>
> enabled => yes
>
> channels => 1-15,17-31
>
> schannel =>
>
> firstcic => 33
>
>
>
> [link-l3]
>
> enabled => yes
>
> linkset => testlink
>
> channels => 1-15,17-31
>
> schannel =>
>
> firstcic => 65
>
>
>
> [link-l4]
>
> enabled => no
>
> linkset => testlink
>
> channels => 1-15,17-31
>
> schannel =>
>
> firstcic => 97
>
>
>
> [host-host.domain.com]
>
> enabled => yes
>
> default_linkset => testlink
>
> ;autopc => yes
>
> opc => 0x27f2 ;13131
>
> dpc => testlink:0x3b48 ;->provider1 (0x334b ;-> provider2)
>
> if-1 => my.host.ip.addr
>
> links => l1:1,l2:2,l3:3,l4:4
>
>
>
> /sbin/lsmod
>
> Module Size Used by
>
> zttranscode 12552 0
>
> tor3e 89116 0
>
> zaptel 186532 184 zttranscode,tor3e
>
> crc_ccitt 6209 1 zaptel
>
> md5 8129 1
>
> ipv6 243425 30
>
> autofs4 25413 0
>
> sunrpc 143909 1
>
> button 10705 0
>
> battery 12997 0
>
> ac 8901 0
>
> hw_random 9685 0
>
> e1000 119249 0
>
> floppy 58193 0
>
> ata_piix 19141 0
>
> libata 105757 1 ata_piix
>
> sg 38369 0
>
> dm_snapshot 21093 0
>
> dm_zero 6337 0
>
> dm_mirror 31173 0
>
> ext3 119113 2
>
> jbd 59609 1 ext3
>
> dm_mod 64617 8 dm_snapshot,dm_zero,dm_mirror
>
> aic79xx 187613 5
>
> sd_mod 20545 9
>
> scsi_mod 119757 4 libata,sg,aic79xx,sd_mod
>
>
>
> cat /proc/interrupts gives shows that tor3e IRQ 217 is in the
> different CPU
> from the eth0 network card:
>
>
>
> CPU0 CPU1 CPU2 CPU3
>
> 0: 2981832 2911004 2910992 2904442 IO-APIC-edge timer
>
> 1: 8 69 50 0 IO-APIC-edge i8042
>
> 8: 1 0 0 0 IO-APIC-edge rtc
>
> 9: 9 0 0 0 IO-APIC-level acpi
>
> 185: 30 0 0 0 IO-APIC-level
> aic79xx
>
> 193: 4999 1944 3374 8368 IO-APIC-level
> aic79xx
>
> 201: 52790 0 0 0 IO-APIC-level eth0
>
> 217: 0 5284112 5280614 20005 IO-APIC-level tor3e
>
> NMI: 0 0 0 0
>
> LOC: 11708215 11708091 11708090 11708212
>
> ERR: 0
>
> MIS: 0
>
>
>
> #lspci -vb gives me the output bellow. (On IRQ 9 there are olso RAID
> bus,
> ethernet, and I mentioned there is no latency)
>
> #lspci -v gives IRQ 217, proved that APIC is running and it is unique.
>
> 03:0a.0 Bridge: PLX Technology, Inc.: Unknown device d44d (rev 01)
>
> Subsystem: PLX Technology, Inc.: Unknown device 9030
>
> Flags: medium devsel, IRQ 9
>
> Memory at fe6f0000 (32-bit, non-prefetchable)
>
> I/O ports at 2000
>
> Memory at fe6e0000 (32-bit, non-prefetchable)
>
> Memory at fe6d0000 (32-bit, non-prefetchable)
>
> Capabilities: [40] Power Management version 1
>
> Capabilities: [48] #06 [0000]
>
> Capabilities: [4c] Vital Product Data
>
>
>
> #dmesg output shows:
>
> ACPI: PCI Interrupt 0000:03:0a.0[A] -> GSI 28 (level, low) -> IRQ 217
>
> Detected Tormenta 3 Quad E1 - TOR3 at 0xfe6e0000/0xfe6d0000 irq 217
>
> Xilinx Chip successfully loaded, configured and started!!
>
> Detected Card number: 0
>
> Tor3: Launching card: 0
>
> Registered Tormenta 3-E PCI
>
> Registered tone zone 4 (United Kingdom)
>
> SPAN 1: Primary Sync Source
>
> SPAN 2: Secondary Sync Source
>
> SPAN 3: Tertiary Sync Source
>
> SPAN 4: Quaternary Sync Source
>
> Zapata Telephony Interface Registered on major 196
>
> Zaptel Version: 1.2.17.1
>
> Zaptel Echo Canceller: KB1
>
> Zaptel: Master changed to Tor3/0/2
>
> Zaptel: Master changed to Tor3/0/3
>
> Zaptel: Master changed to Tor3/0/4
>
> Zaptel: Master changed to Tor3/0/1
>
> Zaptel Transcoder support loaded
>
>
>
> So, my question is: is it possible to make a chan_ss7 work with
> Govarion Tormenta 3 cards at all? Or shell I migrate to the native
> asterisk SS7? I'll appreciate any help.
>
>
>
>
> ___________________________________________________________
> Inbox full of unwanted email? Get leading protection and 1GB storage
> with
> All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 30 May 2007 18:12:49 -0400
> From: "Robert Kenton" <robert.kenton at gmail.com>
> Subject: Re: [asterisk-ss7] Tormenta TOR3 card Asterisk chan_ss7
> To: asterisk-ss7 at lists.digium.com
> Message-ID:
> <9fb0089c0705301512l6a30456ema9ddb6142d35aee0 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hmmm.... It seems a wrong PC configuration.
>
> The link is aligned but after sending the SLTM, it's waitng for the
> SLTA
> which never arrive.
>
> On the remote end, they are sending an UBL message that indicate they
> has
> sent and received a correct SLTM/SLTA.
>
> Verify PC and SLC on both ends (chan_ss7 and Siemens side).
>
> Robert.
>
>
> On 5/30/07, Andrew Somov <asomov12 at yahoo.co.uk> wrote:
>>
>> Tormenta TOR3 card Asterisk chan_ss7 problem. SS7 link is flupping,
>> Need
>> help!!!
>>
>> I was trying to interconnect with several providers, the result was
>> the
>> same. The link is going up for a several seconds, then
>>
>> failed with strings bellow. The channel was compiled without errors
>> and
>> asterisk has started with no warnings.
>>
>> Asterisk-1.2.18, chan_ss7 - 0.9 , chan_oh323, CentOS4.4
>> 2.6.9-48.ELsmp,
>> the zaptel tor3e driver was pulled from http://www.govarion.com/tor3/,
>> the server is dual Intel(R) Xeon(TM) CPU 3.06GHz stepping
>> 09(hyperthreading on).
>>
>>
>>
>> This issue is quite close to
>> http://lists.digium.com/pipermail/asterisk-ss7/2006-July/000410.html
>> and
>>
>>
>>
> http://www.asteriskguru.com/tutorials/
> pci_irq_apic_tdm_ticks_te410p_te405p_n
> oise.html
>>
>> I was explored through all and still have the same result.
>>
>>
>>
>> Getting this error while trying to connect to the provider (DMS
>> switch).
>> the ss7 link status dives:
>>
>> linkset testlink, link l1, schannel 16, INSERVICE, rx: 5, tx: 3/3,
>> sentseq/lastack: 3/3, total 33458560, 33458624
>>
>> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
>> Group reset still in progress for CIC=1, typ=UBL message discarded.
>>
>> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
>> Group reset still in progress for CIC=2, typ=UBL message discarded.
>>
>> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
>> Group reset still in progress for CIC=3, typ=UBL message discarded.
>>
>> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
>> Group reset still in progress for CIC=4, typ=UBL message discarded.
>>
>> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
>> Group reset still in progress for CIC=5, typ=UBL message discarded.
>>
>> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
>> Group reset still in progress for CIC=6, typ=UBL message discarded.
>>
>> May 30 16:48:13 WARNING[12951]: l4isup.c:2284 process_circuit_message:
>> Group reset still in progress for CIC=7, typ=UBL message discarded.
>> etc. (cut)
>>
>> 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'.
>>
>> 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'.
>>
>> May 30 16:48:24 WARNING[12951]: chan_ss7.c:636 monitor_main: MTP is
>> now
>> DOWN on link 'l1'.
>>
>> May 30 16:48:24 NOTICE[12951]: mtp.c:502 mtp_changeover: MTP
>> changeover
>> last_ack=3, last_sent=3, from schannel 16, no INSERVICE schannel found
>>
>> May 30 16:48:24 NOTICE[12951]: mtp.c:506 mtp_changeover: Failover not
>> possible, no other signalling link and no other host available.
>>
>> testlink*CLI> ss7 link status
>>
>> linkset testlink, link l1, schannel 16, DOWN, rx: 2, tx: 4/4,
>> sentseq/lastack: 3/4, total 33467808, 33467872
>>
>> testlink*CLI> ss7 link status
>>
>> linkset testlink, link l1, schannel 16, NOT_ALIGNED, rx: 0, tx: 1/4,
>> sentseq/lastack: 127/127, total 35673520, 35673584
>>
>> May 30 16:49:40 WARNING[12951]: mtp.c:424 t2_timeout: MTP2 timer T2
>> timeout (failed to receive 'O', 'N', or 'E' after sending 'O'),
>> initial
>> alignment failed on link 'l1'.
>>
>>
>>
>> My /etc/asterisk/zapata.conf is empty,
>>
>> cat /etc/zaptel.conf gives
>>
>> span=1,1,0,ccs,hdb3
>>
>> bchan=1-31
>>
>> span=2,2,0,ccs,hdb3
>>
>> bchan=32-62
>>
>> span=3,3,0,ccs,hdb3
>>
>> bchan=63-93
>>
>> span=4,4,0,ccs,hdb3
>>
>> bchan=94-124
>>
>> loadzone = uk
>>
>> defaultzone = uk
>>
>>
>>
>> cat /etc/asterisk/ss7.conf :
>>
>>
>>
>> [linkset-testlink]
>>
>> enabled => yes
>>
>> enable_st => no
>>
>> use_connect => no
>>
>> hunting_policy => even_mru
>>
>> ;t35 => 15000,timeout
>>
>> subservice => 8
>>
>> context => default
>>
>> language => en
>>
>>
>>
>> [link-l1]
>>
>> linkset => testlink
>>
>> enabled => yes
>>
>> channels => 1-15,17-31
>>
>> schannel => 16
>>
>> firstcic => 1
>>
>>
>>
>> [link-l2]
>>
>> linkset => testlink
>>
>> enabled => yes
>>
>> channels => 1-15,17-31
>>
>> schannel =>
>>
>> firstcic => 33
>>
>>
>>
>> [link-l3]
>>
>> enabled => yes
>>
>> linkset => testlink
>>
>> channels => 1-15,17-31
>>
>> schannel =>
>>
>> firstcic => 65
>>
>>
>>
>> [link-l4]
>>
>> enabled => no
>>
>> linkset => testlink
>>
>> channels => 1-15,17-31
>>
>> schannel =>
>>
>> firstcic => 97
>>
>>
>>
>> [host-host.domain.com]
>>
>> enabled => yes
>>
>> default_linkset => testlink
>>
>> ;autopc => yes
>>
>> opc => 0x27f2 ;13131
>>
>> dpc => testlink:0x3b48 ;->provider1 (0x334b ;-> provider2)
>>
>> if-1 => my.host.ip.addr
>>
>> links => l1:1,l2:2,l3:3,l4:4
>>
>>
>>
>> /sbin/lsmod
>>
>> Module Size Used by
>>
>> zttranscode 12552 0
>>
>> tor3e 89116 0
>>
>> zaptel 186532 184 zttranscode,tor3e
>>
>> crc_ccitt 6209 1 zaptel
>>
>> md5 8129 1
>>
>> ipv6 243425 30
>>
>> autofs4 25413 0
>>
>> sunrpc 143909 1
>>
>> button 10705 0
>>
>> battery 12997 0
>>
>> ac 8901 0
>>
>> hw_random 9685 0
>>
>> e1000 119249 0
>>
>> floppy 58193 0
>>
>> ata_piix 19141 0
>>
>> libata 105757 1 ata_piix
>>
>> sg 38369 0
>>
>> dm_snapshot 21093 0
>>
>> dm_zero 6337 0
>>
>> dm_mirror 31173 0
>>
>> ext3 119113 2
>>
>> jbd 59609 1 ext3
>>
>> dm_mod 64617 8 dm_snapshot,dm_zero,dm_mirror
>>
>> aic79xx 187613 5
>>
>> sd_mod 20545 9
>>
>> scsi_mod 119757 4 libata,sg,aic79xx,sd_mod
>>
>>
>>
>> cat /proc/interrupts gives shows that tor3e IRQ 217 is in the
>> different
>> CPU from the eth0 network card:
>>
>>
>>
>> CPU0 CPU1 CPU2 CPU3
>>
>> 0: 2981832 2911004 2910992 2904442 IO-APIC-edge
>> timer
>>
>> 1: 8 69 50 0 IO-APIC-edge
>> i8042
>>
>> 8: 1 0 0 0 IO-APIC-edge rtc
>>
>> 9: 9 0 0 0 IO-APIC-level acpi
>>
>> 185: 30 0 0 0 IO-APIC-level
>> aic79xx
>>
>> 193: 4999 1944 3374 8368 IO-APIC-level
>> aic79xx
>>
>> 201: 52790 0 0 0 IO-APIC-level eth0
>>
>> 217: 0 5284112 5280614 20005 IO-APIC-level
>> tor3e
>>
>> NMI: 0 0 0 0
>>
>> LOC: 11708215 11708091 11708090 11708212
>>
>> ERR: 0
>>
>> MIS: 0
>>
>>
>>
>> #lspci -vb gives me the output bellow. (On IRQ 9 there are olso RAID
>> bus,
>> ethernet, and I mentioned there is no latency)
>>
>> #lspci -v gives IRQ 217, proved that APIC is running and it is unique.
>>
>> 03:0a.0 Bridge: PLX Technology, Inc.: Unknown device d44d (rev 01)
>>
>> Subsystem: PLX Technology, Inc.: Unknown device 9030
>>
>> Flags: medium devsel, IRQ 9
>>
>> Memory at fe6f0000 (32-bit, non-prefetchable)
>>
>> I/O ports at 2000
>>
>> Memory at fe6e0000 (32-bit, non-prefetchable)
>>
>> Memory at fe6d0000 (32-bit, non-prefetchable)
>>
>> Capabilities: [40] Power Management version 1
>>
>> Capabilities: [48] #06 [0000]
>>
>> Capabilities: [4c] Vital Product Data
>>
>>
>>
>> #dmesg output shows:
>>
>> ACPI: PCI Interrupt 0000:03:0a.0[A] -> GSI 28 (level, low) -> IRQ 217
>>
>> Detected Tormenta 3 Quad E1 - TOR3 at 0xfe6e0000/0xfe6d0000 irq 217
>>
>> Xilinx Chip successfully loaded, configured and started!!
>>
>> Detected Card number: 0
>>
>> Tor3: Launching card: 0
>>
>> Registered Tormenta 3-E PCI
>>
>> Registered tone zone 4 (United Kingdom)
>>
>> SPAN 1: Primary Sync Source
>>
>> SPAN 2: Secondary Sync Source
>>
>> SPAN 3: Tertiary Sync Source
>>
>> SPAN 4: Quaternary Sync Source
>>
>> Zapata Telephony Interface Registered on major 196
>>
>> Zaptel Version: 1.2.17.1
>>
>> Zaptel Echo Canceller: KB1
>>
>> Zaptel: Master changed to Tor3/0/2
>>
>> Zaptel: Master changed to Tor3/0/3
>>
>> Zaptel: Master changed to Tor3/0/4
>>
>> Zaptel: Master changed to Tor3/0/1
>>
>> Zaptel Transcoder support loaded
>>
>>
>>
>> So, my question is: is it possible to make a chan_ss7 work with
>> Govarion Tormenta 3 cards at all? Or shell I migrate to the native
>> asterisk SS7? I'll appreciate any help.
>>
>>
>>
>>
>> ___________________________________________________________
>> Inbox full of unwanted email? Get leading protection and 1GB storage
>> with
>> All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> asterisk-ss7 mailing list
>> To UNSUBSCRIBE or update options visit:
>> http://lists.digium.com/mailman/listinfo/asterisk-ss7
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.digium.com/pipermail/asterisk-ss7/attachments/20070530/
> e4c1573e
> /attachment.htm
>
> ------------------------------
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.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 27, Issue 15
> ********************************************
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 31 May 2007 10:48:50 -0300
> From: Juan Carlos Castro y Castro <jcastro at instant.com.br>
> Subject: [asterisk-ss7] Core dump in chan_ss7 -- here's the backtrace
> To: asterisk-ss7 at lists.digium.com
> Message-ID: <465ED242.4000400 at instant.com.br>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> What could be causing it? And another question: since chan_ss7 hasn't
> been updated in the last seven months, is there anyone there developing
> patches for it? My ss7.conf (two machines in a cluster) is below.
>
> Program terminated with signal 11, Segmentation fault.
> #0 0x00d11201 in isup_event_handler (event=0xb7b7caec) at
> l4isup.c:4017
> 4017 ast_log(LOG_DEBUG, "Got ISUP event, typ=%s, cic=%d, pvt.eq=%d
> \n", isupmsg(isup_msg.typ), isup_msg.cic, pvt->equipped);
> (gdb) bt
> #0 0x00d11201 in isup_event_handler (event=0xb7b7caec) at
> l4isup.c:4017
> #1 0x00d1fa67 in cluster_receive_packet (senderix=0, fd=54) at
> cluster.c:570
> #2 0x00d203bd in cluster_thread_main (data=0x0) at cluster.c:712
> #3 0x004373db in start_thread () from /lib/libpthread.so.0
> #4 0x0039126e in clone () from /lib/libc.so.6
>
>
> [linkset-rp1]
> enabled => yes
> enable_st => no
> use_connect => yes
> hunting_policy => even_mru
> subservice => auto
> context => ss7
> language => da
> t35 => 15000,timeout
> subservice => auto
>
> [linkset-rp4]
> enabled => yes
> enable_st => no
> use_connect => yes
> hunting_policy => even_mru
> subservice => auto
> context => ss7
> language => da
> t35 => 15000,timeout
> subservice => auto
>
> [link-l1]
> linkset => rp1
> channels => 1-15,17-31
> schannel => 16
> firstcic => 1
> enabled => yes
>
> [link-l2]
> linkset => rp4
> channels => 1-31
> schannel =>
> firstcic => 1
> enabled => yes
>
> [link-l10]
> linkset => rp4
> channels => 1-15,17-31
> schannel => 16
> firstcic => 129
> enabled => yes
>
> [host-iv-si-mgt-01]
> enabled => yes
> default_linkset => rp1
> opc => 0x3fce ; 16334
> dpc => rp1:0x25cb,rp4:0x25cf ; 9675, 9679
> links => l1:1,l2:2
> if-1 => 192.168.40.106
>
> [host-iv-si-mgt-03]
> enabled => yes
> default_linkset => rp4
> opc => 0x3fce ; 16334
> dpc => rp1:0x25cf,rp4:0x25cb ; 9679, 9675
> links => l10:2
> if-1 => 192.168.40.108
>
> [cluster]
> ; Listen on TCP port 5040
> port => 5040
> l1 => iv-si-mgt-03#if-1
> l2 => iv-si-mgt-03#if-1
> l10 => iv-si-mgt-01#if-1
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 31 May 2007 10:13:32 -0400
> From: "Robert Kenton" <robert.kenton at gmail.com>
> Subject: Re: [asterisk-ss7] Core dump in chan_ss7 -- here's the
> backtrace
> To: asterisk-ss7 at lists.digium.com
> Message-ID:
> <9fb0089c0705310713s2a2b3b24l78540cb29f134dad at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Please, do a 'bt full' to see better the cause.
>
> Rk
>
> On 5/31/07, Juan Carlos Castro y Castro <jcastro at instant.com.br> wrote:
>>
>> What could be causing it? And another question: since chan_ss7 hasn't
>> been updated in the last seven months, is there anyone there
>> developing
>> patches for it? My ss7.conf (two machines in a cluster) is below.
>>
>> Program terminated with signal 11, Segmentation fault.
>> #0 0x00d11201 in isup_event_handler (event=0xb7b7caec) at
>> l4isup.c:4017
>> 4017 ast_log(LOG_DEBUG, "Got ISUP event, typ=%s, cic=%d,
>> pvt.eq=%d
>> \n", isupmsg(isup_msg.typ), isup_msg.cic, pvt->equipped);
>> (gdb) bt
>> #0 0x00d11201 in isup_event_handler (event=0xb7b7caec) at
>> l4isup.c:4017
>> #1 0x00d1fa67 in cluster_receive_packet (senderix=0, fd=54) at
>> cluster.c:570
>> #2 0x00d203bd in cluster_thread_main (data=0x0) at cluster.c:712
>> #3 0x004373db in start_thread () from /lib/libpthread.so.0
>> #4 0x0039126e in clone () from /lib/libc.so.6
>>
>>
>> [linkset-rp1]
>> enabled => yes
>> enable_st => no
>> use_connect => yes
>> hunting_policy => even_mru
>> subservice => auto
>> context => ss7
>> language => da
>> t35 => 15000,timeout
>> subservice => auto
>>
>> [linkset-rp4]
>> enabled => yes
>> enable_st => no
>> use_connect => yes
>> hunting_policy => even_mru
>> subservice => auto
>> context => ss7
>> language => da
>> t35 => 15000,timeout
>> subservice => auto
>>
>> [link-l1]
>> linkset => rp1
>> channels => 1-15,17-31
>> schannel => 16
>> firstcic => 1
>> enabled => yes
>>
>> [link-l2]
>> linkset => rp4
>> channels => 1-31
>> schannel =>
>> firstcic => 1
>> enabled => yes
>>
>> [link-l10]
>> linkset => rp4
>> channels => 1-15,17-31
>> schannel => 16
>> firstcic => 129
>> enabled => yes
>>
>> [host-iv-si-mgt-01]
>> enabled => yes
>> default_linkset => rp1
>> opc => 0x3fce ; 16334
>> dpc => rp1:0x25cb,rp4:0x25cf ; 9675, 9679
>> links => l1:1,l2:2
>> if-1 => 192.168.40.106
>>
>> [host-iv-si-mgt-03]
>> enabled => yes
>> default_linkset => rp4
>> opc => 0x3fce ; 16334
>> dpc => rp1:0x25cf,rp4:0x25cb ; 9679, 9675
>> links => l10:2
>> if-1 => 192.168.40.108
>>
>> [cluster]
>> ; Listen on TCP port 5040
>> port => 5040
>> l1 => iv-si-mgt-03#if-1
>> l2 => iv-si-mgt-03#if-1
>> l10 => iv-si-mgt-01#if-1
>>
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> asterisk-ss7 mailing list
>> To UNSUBSCRIBE or update options visit:
>> http://lists.digium.com/mailman/listinfo/asterisk-ss7
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.digium.com/pipermail/asterisk-ss7/attachments/20070531/
> 89346f13/attachment.htm
>
> ------------------------------
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.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 27, Issue 16
> ********************************************
>
>
>
>
>
>
> ___________________________________________________________
> Yahoo! Messenger - with free PC-PC calling and photo sharing.
> http://uk.messenger.yahoo.com
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-ss7 mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-ss7
More information about the asterisk-ss7
mailing list