libss7 random problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, this is my first post on this list.

I've trying to setup a libss7 server and pri (both svn version) on the same
server.  The ss7 conection is on a MSC ZTE ZXG10 and the pri is on a avaya
pbx.  That works!!, but (always exist a but) randomly crash!, the signallink
crash and 2 linksets crash too, means the spans are alarms (yellow) and the
signalling is reinitializated, that happend two o three times at night.
data for debugging
Server is a poweredge 2900

lspci -v
09:01.0 Communication controller: Digium, Inc. Wildcard TE410P quad-span
T1/E1/J1 card 3.3V (rev 02)
        Subsystem: Unknown device 0003:0000
        Flags: bus master, medium devsel, latency 32, IRQ 90
        Memory at d5effc00 (32-bit, non-prefetchable) [size=128]

09:02.0 Communication controller: Digium, Inc. Wildcard TE410P quad-span
T1/E1/J1 card 3.3V (rev 02)
        Subsystem: Unknown device 0003:0000
        Flags: bus master, medium devsel, latency 32, IRQ 98
        Memory at d5eff800 (32-bit, non-prefetchable) [size=128]

@ivr-00:~/sources/TRUNK$ cat /proc/interrupts 
           CPU0       CPU1       CPU2       CPU3       
  0:  259228498          0          0          0    IO-APIC-edge  timer
  1:          3          0          0          0    IO-APIC-edge  i8042
  8:          1          0          0          0    IO-APIC-edge  rtc
  9:          0          0          0          0   IO-APIC-level  acpi
 12:          4          0          0          0    IO-APIC-edge  i8042
 66:         34          0          0          0   IO-APIC-level
uhci_hcd:usb1, uhci_hcd:usb3, ehci_hcd:usb4
 74:          0          0          0          0   IO-APIC-level
uhci_hcd:usb2
 82:        145          0          0          0   IO-APIC-level  libata
 90:  259093992          0          0          0   IO-APIC-level  wct4xxp
 98:  259090163          0          0          0   IO-APIC-level  wct4xxp
106:      41172          0          0          0         PCI-MSI  eth0
169:     342665          0          0          0   IO-APIC-level  ioc0
NMI:      38582       6356       1906       3262 
LOC:  259129031  259129990  259128878  259129827 
ERR:          0
MIS:          0

@ivr-00:~/sources/TRUNK$ uname -a
Linux ivr-00 2.6.18-53.1.14.el5 #1 SMP Wed Mar 5 11:37:38 EST 2008 x86_64
x86_64 x86_64 GNU/Linux

Zaptel.conf
# CONFIGURACION CHILE
loadzone=cl
defaultzone=cl

span=1,1,0,ccs,hdb3,yellow
bchan=1-15,17-31
dchan=16

# PRI
span=2,0,0,ccs,hdb3
bchan=32-62

span=3,0,0,ccs,hdb3,yellow
bchan=63-93

span=4,1,0,ccs,hdb3,yellow
bchan=94-124

span=5,0,0,ccs,hdb3,yellow
bchan=125-155

span=6,0,0,ccs,hdb3,yellow
bchan=156-186

span=7,0,0,ccs,hdb3,yellow
bchan=187-217

span=8,0,0,ccs,hdb3,yellow
bchan=218-248

Zapata.conf
[trunkgroups]

[channels]
language=es
context=ss7_contexto
pridialplan=dynamic
internationalprefix = 
nationalprefix = 
localprefix = 
unknownprefix = 
priindication = outofband
signalling=ss7
usecallerid=yes
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
canpark=no

group=1
ss7type = itu
ss7_called_nai=dynamic
ss7_calling_nai=dynamic
ss7_internationalprefix = 
ss7_nationalprefix = 
ss7_subscriberprefix = 
ss7_unknownprefix = 

linkset = 1
pointcode = 6171
adjpointcode = 2572
defaultdpc = 2572
networkindicator=national
cicbeginswith = 1
sigchan = 16
channel = 1-15
cicbeginswith = 17
channel = 17-31

; PRI
switchtype=national
context=avaya
signalling=pri_net
inmediate=no
group=2
channel => 32-46
channel => 48-62

Alarms
[2008-04-18 22:34:51] DEBUG[20038] chan_zap.c: Bad FCS
[2008-04-18 22:35:09] DEBUG[20038] chan_zap.c: Bad FCS
[2008-04-18 22:35:12] DEBUG[20038] chan_zap.c: Monitor doohicky got event
Alarm on channel 1
[2008-04-18 22:35:12] WARNING[20038] chan_zap.c: Detected alarm on channel
1: Yellow Alarm
[2008-04-18 22:35:12] DEBUG[20038] chan_zap.c: Monitor doohicky got event
Alarm on channel 2
[2008-04-18 22:35:12] WARNING[20038] chan_zap.c: Detected alarm on channel
2: Yellow Alarm
[2008-04-18 22:35:12] NOTICE[20038] chan_zap.c: PRI got event: Alarm (4) on
Primary D-channel of span 2
[2008-04-18 22:35:12] WARNING[20038] chan_zap.c: No D-channels available!
Using Primary channel 47 as D-channel anyway!
[2008-04-18 22:35:12] DEBUG[20038] chan_zap.c: Got event Alarm (4) on
D-channel for span 2
[2008-04-18 22:35:12] ERROR[20038] chan_zap.c: Alarm on link!
[2008-04-18 22:35:12] VERBOSE[20038] logger.c: --- SS7 Down ---

hope anyone can help

regards

Jorge Valencia G.
jvalencia at chile.com
56 9 94426869




[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Backpacking]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux