Hi All,
Having a troubles interconnecting via libss7. I would love to use the chan_ss7 driver, but, as soon it doesn't support a-link, had to switch to libss7. Since my last post http://lists.digium.com/pipermail/asterisk-ss7/2007-May/001284.html ,problem was solved and the box is working with no interrupts at all, customer even forgot what equipment does he has :-).
Components are used:
Asterisk 1.6.0.b7.1
libss7-trunk
zaptel 1.4.7.1 patched for tor3e cards
The target is to connect two different vendors, lets say first "east", second "west".
Both are using a-links, both connections have 4E1, so, "east" is patched at card 1, therefore "west" to card 2. Both vendors are suppl by our the only one OPC.
Here are outputs:
*********************************
lspci -v
06:01.0 Bridge: PLX Technology, Inc.: Unknown device 4000 (rev 01)
Subsystem: PLX Technology, Inc.: Unknown device 9030
Flags: medium devsel, IRQ 225
Memory at fdff0000 (32-bit, non-prefetchable) [size=128]
I/O ports at 5000 [size=128]
Memory at fdfe0000 (32-bit, non-prefetchable) [size=2K]
Memory at fdfd0000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [40] Power Management version 1
Capabilities: [48] #06 [0000]
Capabilities: [4c] Vital Product Data
06:02.0 Bridge: PLX Technology, Inc.: Unknown device 4000 (rev 01)
Subsystem: PLX Technology, Inc.: Unknown device 9030
Flags: medium devsel, IRQ 233
Memory at fdfc0000 (32-bit, non-prefetchable) [size=128]
I/O ports at 5080 [size=128]
Memory at fdfb0000 (32-bit, non-prefetchable) [size=2K]
Memory at fdfa0000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [40] Power Management version 1
Capabilities: [48] #06 [0000]
Capabilities: [4c] Vital Product Data
********************************
cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 4067498 4069784 4069795 4069751 IO-APIC-edge timer
1: 2 3 2 2 IO-APIC-edge i8042
8: 1 0 0 0 IO-APIC-edge rtc
9: 0 0 0 0 IO-APIC-level acpi
12: 0 7 13 46 IO-APIC-edge i8042
14: 188 72712 72431 489 IO-APIC-edge ide0
169: 0 0 0 0 IO-APIC-level uhci_hcd, uhci_hcd
177: 0 0 0 0 IO-APIC-level uhci_hcd
185: 0 0 0 0 IO-APIC-level uhci_hcd
193: 0 0 0 0 IO-APIC-level ehci_hcd
201: 53413 0 4 8 IO-APIC-level eth0
217: 8979 1974 2444 8069 IO-APIC-level cciss0
225: 7041563 757525 230056 7655588 IO-APIC-level tor3e
233: 1700415 1510306 2281990 2037810 IO-APIC-level tor3e
NMI: 0 0 0 0
LOC: 16189329 16189397 16183755 16183754
ERR: 0
MIS: 0
**********************************
ztcfg -v ; note, we see spans from 1 to 8 here
Zaptel Version: 1.4.7.1
Echo Canceller: MG2
Configuration
======================
SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 2: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 3: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 4: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 5: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 6: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 7: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 8: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
241 channels to configure.
********************************
*span1 is for "east" and has signaling link at 16th channel
*span5 is for "west" and has the signalling link at 1st channel
cat /etc/zaptel.conf
# Autogenerated by /usr/sbin/zapconf on Sun Apr 20 10:44:09 2008 -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#
# Span 1: Tor3/0/1 "Tormenta 3 (PCI) Quad E1 Card 0 Span 1" HDB3/CCS
loadzone=uk
defaultzone=uk
span=1,0,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
span=2,0,0,ccs,hdb3
bchan=32-46,48-62
#dchan=47
span=3,0,0,ccs,hdb3
bchan=63-77,79-93
#dchan=78
span=4,0,0,ccs,hdb3
bchan=94-108,110-124
#dchan=109
span=5,1,0,ccs,hdb3
bchan=126-139,141-155
dchan=125
span=6,0,0,ccs,hdb3
bchan=156-170,172-186
#dchan=171
span=7,0,0,ccs,hdb3
bchan=187-201,203-217
#dchan=202
span=8,0,0,ccs,hdb3
bchan=218-232,234-248
#dchan=233
***************************************
* accordingly: linkset 1 serves "east" NI = national and linkset2 serves "west" NI = international
* OPC (the only one) are the same for both
cat /etc/asterisk/zapata.conf
[channels]
;context=zapIncoming
;switchtype=dms100
usecallerid=yes
hidecallerid=no
;echocancel=yes
echocancelwhenbridged=yes
musiconhold=default
linkset = 1
signalling=ss7
ss7type = itu
;ss7_called_nai=national
;ss7_calling_nai=national
;group = 1
context = default
language = en
networkindicator = national
pointcode = 13131
defaultdpc = 14346
adjpointcode = 14346
cicbeginswith = 1
sigchan = 16
channel = 1-15,17-31
cicbeginswith = 33
channel = 32-46,48-62
cicbeginswith = 65
channel = 63-77,79-93
cicbeginswith = 93
channel = 94-108,110-124
linkset = 2
signalling=ss7
ss7type = itu
;group = 1
context = default
language = en
networkindicator = international
pointcode = 13131
defaultdpc = 8994
adjpointcode = 8999
cicbeginswith = 2
sigchan = 125
channel = 126-139,141-155
cicbeginswith = 33
channel = 156-170,172-186
cicbeginswith = 65
channel = 187-201,203-217
cicbeginswith = 93
channel = 218-232,234-248
*************************
ztcfg -vv ;gives:
Zaptel Version: 1.4.7.1
Echo Canceller: MG2
Configuration
======================
SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 2: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 3: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 4: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 5: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 6: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 7: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 8: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
Channel map:
Channel 01: Clear channel (Default) (Slaves: 01)
--snip--
Channel 15: Clear channel (Default) (Slaves: 15)
Channel 16: D-channel (Default) (Slaves: 16)
Channel 17: Clear channel (Default) (Slaves: 17)
--snip--
Channel 124: Clear channel (Default) (Slaves: 124)
Channel 125: D-channel (Default) (Slaves: 125)
Channel 126: Clear channel (Default) (Slaves: 126)
--snip--
Channel 247: Clear channel (Default) (Slaves: 247)
Channel 248: Clear channel (Default) (Slaves: 248)
241 channels to configure.
***************************
At startup gives:
asterisk -vvvvvvvvvvvvvvvvvvvvcg
--snip--
-- Registered channel 1, SS7 signalling
-- Registered channel 2, SS7 signalling
--snip--
-- Registered channel 247, SS7 signalling
-- Registered channel 248, SS7 signalling
-- Automatically generated pseudo channel
== Starting SS7 linkset on span 1
== Starting SS7 linkset on span 2
== Registered channel type 'Zap' (Zapata Telephony Driver 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)
SIP channel loading...
== Parsing '/etc/asterisk/sip.conf': --- SS7 Down ---
--snip--
[Apr 20 15:25:20] ERROR[11304]: chan_zap.c:9752 zt_ss7_error: Received message destined for point code 0x380a but we're 0x334b. Dropping
[Apr 20 15:25:20] ERROR[11304]: chan_zap.c:9752 zt_ss7_error: Received error from mtp3 layer: -1
[Apr 20 15:25:20] ERROR[11304]: chan_zap.c:9752 zt_ss7_error: Received message destined for point code 0x380a but we're 0x334b. Dropping
[Apr 20 15:25:20] ERROR[11304]: chan_zap.c:9752 zt_ss7_error: Received error from mtp3 layer: -1
**** take a look at alarms- whatever I tried to adjust, it sending different error warnings.
So, my question is, will zaptel-libss7 support multiple cards configuration for different linksets?
Thanks
Andrew
__________________________________________________________
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
|