× Questions about B100/200/400/800 ISDN BRI Cards

B200M on Alix

7 years 1 week ago #8075 by g.grandis
Hi, i found your address (i added you to MSN too) on your forum. I installed B200M mini-pci card on alix boards followinf this giude: http://downloads.openvox.cn/pub/manuals/V2.2/English/B200M_on_DAHDI_User_Manual.pdf but i have some problem with ISDN telco.
This is my software installation:
1.
Libpri
2.
Libss7
3.
Dahdi (download from your website)
4.
Asterisk 1.6.2.18

I configured one port (span 2) in NT mode and connected on legacy PBX and it works fine:
-- Accepting overlap call from '0405' to '<unspecified>' on channel 0/2, span 2
-- Starting simple switch on 'DAHDI/5-1'
……
-- Called 315
-- SIP/315-00000001 is ringing

The first port instead, has been connected to my telco (TelecomItalia) and here i have some problem: the port works only for some minuts and when the d-channels goes down, it never will come back up. I cannot make and receive calls:

== Primary D-Channel on span 1 up
-- Accepting call from '085445XXXX' to '85415XXXX' on channel 0/1, span 1
-- Executing [854151775@pstn-incoming:1] Answer("DAHDI/1-1", "") in new stack
-- Executing [854151775@pstn-incoming:2] Wait("DAHDI/1-1", "3") in new stack
[May 15 11:48:20] NOTICE[4576]: chan_dahdi.c:6501 dahdi_handle_event: Alarm cleared on channel 1
[May 15 11:48:20] NOTICE[4470]: chan_dahdi.c:9811 handle_init_event: Alarm cleared on channel 2
[May 15 11:48:20] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 1
-- Executing [854151775@pstn-incoming:3] SayDigits("DAHDI/1-1", "085415XXXX") in new stack
-- <DAHDI/1-1> Playing 'digits/0.gsm' (language 'it')
-- <DAHDI/1-1> Playing 'digits/8.gsm' (language 'it')
-- <DAHDI/1-1> Playing 'digits/5.gsm' (language 'it')
-- <DAHDI/1-1> Playing 'digits/4.gsm' (language 'it')
-- <DAHDI/1-1> Playing 'digits/1.gsm' (language 'it')
-- <DAHDI/1-1> Playing 'digits/5.gsm' (language 'it')
-- <DAHDI/1-1> Playing 'digits/.gsm' (language 'it')
-- <DAHDI/1-1> Playing 'digits/.gsm' (language 'it')
-- <DAHDI/1-1> Playing 'digits/.gsm' (language 'it')
-- <DAHDI/1-1> Playing 'digits/.gsm' (language 'it')
-- Executing [85415XXXX@pstn-incoming:4] Hangup("DAHDI/1-1", "") in new stack
== Spawn extension (pstn-incoming, 85415XXXX, 4) exited non-zero on 'DAHDI/1-1'
-- Hungup 'DAHDI/1-1'
[May 15 11:48:51] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[May 15 11:49:02] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[May 15 11:49:12] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[May 15 11:49:22] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[May 15 11:49:33] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[May 15 11:49:43] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[May 15 11:49:53] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[May 15 11:50:04] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[May 15 11:50:14] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[May 15 11:50:25] WARNING[4470]: chan_dahdi.c:5948 handle_alarms: Detected alarm on channel 1: Red Alarm
[May 15 11:50:25] WARNING[4470]: chan_dahdi.c:5948 handle_alarms: Detected alarm on channel 2: Red Alarm
[May 15 11:50:25] NOTICE[4468]: chan_dahdi.c:13133 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1

This is my /proc/interrupts

CPU0
0: 17605365 XT-PIC-XT timer
2: 0 XT-PIC-XT cascade
3: 6 XT-PIC-XT serial
4: 6 XT-PIC-XT serial
8: 0 XT-PIC-XT rtc0
9: 70167679 XT-PIC-XT b4xxp
10: 170808 XT-PIC-XT eth0
12: 1 XT-PIC-XT ehci_hcd:usb1, ohci_hcd:usb2
14: 60491 XT-PIC-XT pata_amd
15: 0 XT-PIC-XT pata_amd
NMI: 0 Non-maskable interrupts
LOC: 0 Local timer interrupts
SPU: 0 Spurious interrupts
PMI: 0 Performance monitoring interrupts
PND: 0 Performance pending work
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
THR: 0 Threshold APIC interrupts
MCE: 0 Machine check exceptions
MCP: 0 Machine check polls
ERR: 0
MIS: 0

/etc/dahdi/system.conf

# Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) RED
span=1,1,0,ccs,ami
# termtype: te
bchan=1-2
hardhdlc=3
echocanceller=mg2,1-2

# Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" RED
span=2,0,0,ccs,ami
# termtype: te
bchan=4-5
hardhdlc=6
echocanceller=mg2,4-5

# Global data
loadzone = it
defaultzone = it

and my /etc/asterisk/chan_dahdi.conf:
[channels]
language=it
switchtype=euroisdn
signalling=bri_cpe_ptmp
cidwithheld = Numero Privato
prilocaldialplan=national
pridialplan=unknown
unknownprefix=0
nationalprefix=0
internationalprefix=00
resetinterval=never
facilityenable = yes
usecallingpres=yes
usecallerid=yes
hidecallerid=no
faxdetect=outgoing
callerid=asreceived
echocancel=yes
echocancelwhenbridged=no
echotraining=no
overlapdial=no
immediate = no
musiconhold=default
context=pstn-incoming
group=1
callgroup=1
pickupgroup=1
channel => 1-2

switchtype=euroisdn
signalling=bri_net
cidwithheld = Numero Privato
pridialplan=unknown
prilocaldialplan=unknown
nationalprefix=0
internationalprefix=00
unknownprefix=8
facilityenable = yes
usecallingpres=yes
usecallerid=yes
hidecallerid=no
context=polaris-incoming
overlapdial=yes
immediate=no
group=2
callgroup=2
pickupgroup=2
channel => 4-5

vivo-pbx*CLI> dahdi show status
Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO
B4XXP (PCI) Card 0 Span 1 RED 0 0 0 CCS AMI 0 db (CSU)/0-133 feet (DSX-1)
B4XXP (PCI) Card 0 Span 2 OK 0 0 0 CCS AMI 0 db (CSU)/0-133 feet (DSX-1)
vivo-pbx*CLI>

vivo-pbx*CLI> pri show spans
PRI span 1/0: Provisioned, In Alarm, Down, Active
PRI span 2/0: Provisioned, Up, Active
vivo-pbx*CLI>

Why one port works and the one no? I don’t thingh is an hardware problem…
Time to create page: 0.041 seconds
Powered by Kunena Forum