Beronet BN4S0 + Bristuff + 3 hfcpci

maroc

Neuer User
Mitglied seit
9 Mrz 2006
Beiträge
9
Punkte für Reaktionen
0
Punkte
0
Hallo,

versuche seit tagen die Beronet BN4SO mit Bristuff und Patch wie nach den Anleitungen:

1. [HowTo] Debian 4.0 (Etch) – Bristuff Installation -Kernel 2.6.18-5
http://www.ip-phone-forum.de/showthread.php?t=155067

2. bristuff Patch für BeroNet Karten
http://www.ip-phone-forum.de/showthread.php?t=113713&highlight=bristuff+beronet

zu installieren leider ohne richtigen Erfolg!! :(

Laut Anleitung sollten die LED's der Karte bei erfolgreich geladeten Treiber leuchten.



Meine Vorstellung:

1 x Beronet BN4SO alle 4x Ports als NT ( sollen 6 ISDN Telefone angeschlossen werden, evtl später auch 8 Telefone)

3 x hfcpci als TE ( jede Karte an einer Amtsleitungen (ISDN-NTBA))

Ich bekomme die Fehlermeldung bei Asterisk, wer kann mir evtl ein Tip geben!
Ich kann per Sip raus telefonieren, nur mit ISDN klappt leider noch nicht.

Auszug Asterisk :
Code:
*CLI> Jan 11 16:46:34 WARNING[2310]: chan_zap.c:6887 handle_init_event: Detected alarm on channel 1: Red Alarm
Jan 11 16:46:34 WARNING[2310]: chan_zap.c:6887 handle_init_event: Detected alarm on channel 2: Red Alarm
Jan 11 16:46:34 WARNING[2310]: chan_zap.c:6887 handle_init_event: Detected alarm on channel 4: Red Alarm
Jan 11 16:46:34 WARNING[2310]: chan_zap.c:6887 handle_init_event: Detected alarm on channel 5: Red Alarm
Jan 11 16:46:34 WARNING[2310]: chan_zap.c:6887 handle_init_event: Detected alarm on channel 7: Red Alarm
Jan 11 16:46:34 WARNING[2310]: chan_zap.c:6887 handle_init_event: Detected alarm on channel 8: Red Alarm
Jan 11 16:46:34 WARNING[2310]: chan_zap.c:6887 handle_init_event: Detected alarm on channel 10: Red Alarm
Jan 11 16:46:34 WARNING[2310]: chan_zap.c:6887 handle_init_event: Detected alarm on channel 11: Red Alarm
Jan 11 16:46:34 NOTICE[2306]: chan_zap.c:9099 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1
Jan 11 16:46:34 WARNING[2306]: chan_zap.c:2674 pri_find_dchan: No D-channels available!  Using Primary channel 3 as D-channel anyway!
Jan 11 16:46:34 NOTICE[2307]: chan_zap.c:9099 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 2
Jan 11 16:46:34 WARNING[2307]: chan_zap.c:2674 pri_find_dchan: No D-channels available!  Using Primary channel 6 as D-channel anyway!
Jan 11 16:46:34 NOTICE[2308]: chan_zap.c:9099 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 3
Jan 11 16:46:34 WARNING[2308]: chan_zap.c:2674 pri_find_dchan: No D-channels available!  Using Primary channel 9 as D-channel anyway!
Jan 11 16:46:34 NOTICE[2309]: chan_zap.c:9099 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 4
Jan 11 16:46:34 WARNING[2309]: chan_zap.c:2674 pri_find_dchan: No D-channels available!  Using Primary channel 12 as D-channel anyway!
Jan 11 16:46:34 NOTICE[2310]: chan_zap.c:6868 handle_init_event: Alarm cleared on channel 1
Jan 11 16:46:34 NOTICE[2310]: chan_zap.c:6868 handle_init_event: Alarm cleared on channel 2
Jan 11 16:46:34 NOTICE[2310]: chan_zap.c:6868 handle_init_event: Alarm cleared on channel 4
Jan 11 16:46:34 NOTICE[2310]: chan_zap.c:6868 handle_init_event: Alarm cleared on channel 5
Jan 11 16:46:34 NOTICE[2310]: chan_zap.c:6868 handle_init_event: Alarm cleared on channel 7
Jan 11 16:46:34 NOTICE[2310]: chan_zap.c:6868 handle_init_event: Alarm cleared on channel 8
Jan 11 16:46:34 NOTICE[2310]: chan_zap.c:6868 handle_init_event: Alarm cleared on channel 10
Jan 11 16:46:34 NOTICE[2310]: chan_zap.c:6868 handle_init_event: Alarm cleared on channel 11
Jan 11 16:46:34 NOTICE[2306]: chan_zap.c:9099 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 1
Jan 11 16:46:34 NOTICE[2307]: chan_zap.c:9099 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 2
Jan 11 16:46:34 NOTICE[2308]: chan_zap.c:9099 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 3
Jan 11 16:46:34 NOTICE[2309]: chan_zap.c:9099 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 4


Auszug ztcfg -vvv:
Code:
voip:/usr/src/bristuff-0.3.0-PRE-1y-h/qozap# ztcfg -vvv

Zaptel Configuration
======================

SPAN 1: CCS/ AMI Build-out: 399-533 feet (DSX-1)
SPAN 2: CCS/ AMI Build-out: 399-533 feet (DSX-1)
SPAN 3: CCS/ AMI Build-out: 399-533 feet (DSX-1)
SPAN 4: CCS/ AMI Build-out: 399-533 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Slaves: 01)
Channel 02: Clear channel (Default) (Slaves: 02)
Channel 03: D-channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: D-channel (Default) (Slaves: 06)
Channel 07: Clear channel (Default) (Slaves: 07)
Channel 08: Clear channel (Default) (Slaves: 08)
Channel 09: D-channel (Default) (Slaves: 09)
Channel 10: Clear channel (Default) (Slaves: 10)
Channel 11: Clear channel (Default) (Slaves: 11)
Channel 12: D-channel (Default) (Slaves: 12)

12 channels configured.


lspci:
Code:
voip:/usr/src/bristuff-0.3.0-PRE-1y-h/qozap# lspci -v
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge
        Subsystem: VIA Technologies, Inc. Unknown device 0000
        Flags: bus master, 66MHz, medium devsel, latency 8
        Memory at e0000000 (32-bit, prefetchable) [size=128M]
        Capabilities: [a0] AGP version 2.0
        Capabilities: [c0] Power Management version 2

00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00 [Normal decode])
        Flags: bus master, 66MHz, medium devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: dde00000-dfefffff
        Prefetchable memory behind bridge: cdd00000-ddcfffff
        Capabilities: [80] Power Management version 2

00:06.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)
        Subsystem: Cologne Chip Designs GmbH Unknown device b560
        Flags: medium devsel, IRQ 193
        I/O ports at ec00 [size=8]
        Memory at dffff000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2

00:07.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02)
        Subsystem: Cologne Chip Designs GmbH ISDN Board
        Flags: bus master, medium devsel, latency 16, IRQ 5
        I/O ports at e800 [size=8]
        Memory at dfffef00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 1

00:08.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02)
        Subsystem: Cologne Chip Designs GmbH ISDN Board
        Flags: bus master, medium devsel, latency 16, IRQ 10
        I/O ports at e400 [size=8]
        Memory at dfffee00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 1

00:0a.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02)
        Subsystem: Cologne Chip Designs GmbH ISDN Board
        Flags: bus master, medium devsel, latency 16, IRQ 10
        I/O ports at e000 [size=8]
        Memory at dfffed00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 1

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
        Subsystem: Micro-Star International Co., Ltd. Unknown device 7120
        Flags: bus master, medium devsel, latency 32, IRQ 169
        I/O ports at d400 [size=32]
        Capabilities: [80] Power Management version 2

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
        Subsystem: Micro-Star International Co., Ltd. Unknown device 7120
        Flags: bus master, medium devsel, latency 32, IRQ 169
        I/O ports at d800 [size=32]
        Capabilities: [80] Power Management version 2

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
        Subsystem: Micro-Star International Co., Ltd. Unknown device 7120
        Flags: bus master, medium devsel, latency 32, IRQ 169
        I/O ports at dc00 [size=32]
        Capabilities: [80] Power Management version 2

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
        Subsystem: Micro-Star International Co., Ltd. Unknown device 7120
        Flags: bus master, medium devsel, latency 32, IRQ 169
        Memory at dfffec00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2

00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
        Subsystem: VIA Technologies, Inc. Unknown device 0000
        Flags: bus master, stepping, medium devsel, latency 0
        Capabilities: [c0] Power Management version 2

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
        Subsystem: Micro-Star International Co., Ltd. Unknown device 7120
        Flags: bus master, medium devsel, latency 32, IRQ 255
        I/O ports at fc00 [size=16]
        Capabilities: [c0] Power Management version 2

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
        Subsystem: Micro-Star International Co., Ltd. Unknown device 7120
        Flags: medium devsel, IRQ 185
        I/O ports at d000 [size=256]
        Capabilities: [c0] Power Management version 2

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
        Subsystem: Micro-Star International Co., Ltd. Unknown device 7120
        Flags: bus master, medium devsel, latency 32, IRQ 177
        I/O ports at cc00 [size=256]
        Memory at dfffeb00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 2

01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2) (prog-if 00 [VGA])
        Subsystem: Micro-Star International Co., Ltd. MSI GeForce2 MX400 Pro32S [MS-8817]
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 11
        Memory at de000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (32-bit, prefetchable) [size=128M]
        Expansion ROM at dfef0000 [disabled] [size=64K]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 2.0

zaptel:
Code:
loadzone=de
defaultzone=de
# qozap span definitions
# most of the values should be bogus because we are not really zaptel

#span=1,1,3,ccs,ami
#span=2,2,3,ccs,ami
#span=3,3,3,ccs,ami
#span=4,4,3,ccs,ami

span=1,0,3,ccs,ami
span=2,0,3,ccs,ami
span=3,0,3,ccs,ami
span=4,0,3,ccs,ami

bchan=1,2
dchan=3
bchan=4,5
dchan=6
bchan=7,8
dchan=9
bchan=10,11
dchan=12

zapata.conf:
Code:
;
; Zapata telephony interface
;
; Configuration file

[channels]
;
; Default language
;
language=de
;
; Default context
;
;
switchtype = euroisdn

; p2mp TE mode (for connecting ISDN lines in point-to-multipoint mode)
;signalling = bri_cpe_ptmp
; p2p TE mode (for connecting ISDN lines in point-to-point mode)
;signalling = bri_cpe
; p2mp NT mode (for connecting ISDN phones in point-to-multipoint mode)
signalling = bri_net_ptmp
; p2p NT mode (for connecting an ISDN pbx in point-to-point mode)
;signalling = bri_net

pridialplan = local
prilocaldialplan = dynamic
nationalprefix = 0
internationalprefix = 00

priindication = passthrough

echocancel = yes

context=demo
group = 1
; S/T port 1
channel => 1-2

group = 2
; S/T port 2
channel => 4-5

group = 3
; S/T port 3
channel => 7-8

group = 4
; S/T port 4
channel => 10-11

Mein System:

AMD Athlon 2200+
Debian Etch 4.0 r2
Kernel 2.6.18-5-486
Asterisk 1.2.19
Bristuff-0.3.0-PRE-1y-h
Beronet Patch: qozap_beronet_BRIstuff-0.3.0PRE-1y-h.patch.bz2
1x Beronet BN4S0 Karte
3x hfcpci (Conrad)
 
Zuletzt bearbeitet:
..Asterisk findet meine Beronet BN4S0 aber als TE

Asterisk
Code:
*CLI> zap show status
Description                              Alarms     IRQ        bpviol     CRC4
quadBRI PCI ISDN Card 1 Span 1 [TE] (ca· OK         0          0          0
quadBRI PCI ISDN Card 1 Span 2 [TE] (ca· OK         0          0          0
quadBRI PCI ISDN Card 1 Span 3 [TE] (ca· OK         0          0          0
quadBRI PCI ISDN Card 1 Span 4 [TE] (ca· OK         0          0          0
*CLI>
 
..keiner da, der mir evtl. ein Tip geben kann :-(
 
Mal die Jumper/DIP Schalter auf der Karte gechecked ? Manchmal kan man da auch das Verhalten der Karte festlegen (TE/NT). Kenne die Beronet Karte allerdnigs nicht.

Grüße
Michael
 
Hallo maroc,
..Asterisk findet meine Beronet BN4S0 aber als TE
Wenn die Ports als TE-Ports gestartet werden, dann hast Du beim Laden des qozap Kernelmoduls den falschen ports-Parameter verwendet.

Außerdem mußt Du die Jumper auf der BN4S0 umsetzen, falls noch nicht geschehen.

Gruß
Henning
 
Hallo Zusammen,

Wenn die Ports als TE-Ports gestartet werden, dann hast Du beim Laden des qozap Kernelmoduls den falschen ports-Parameter verwendet.

..wie starte ich den die Ports mit den richtigen Parameter um Sie als NT laufen zu lassen ?


Außerdem mußt Du die Jumper auf der BN4S0 umsetzen, falls noch nicht geschehen.
..also die Beronet BN4SO Karte ist schon richtig gejumpert, genau wie nach der Anleitung von Beronet.



..also ich wäre für jeden Tip dankbar, damit ich am Wochenende wieder was zu tun habe ;)

Freundliche Grüße
Maroc
 

Neueste Beiträge

Statistik des Forums

Themen
244,860
Beiträge
2,219,677
Mitglieder
371,577
Neuestes Mitglied
bigt2014
Holen Sie sich 3CX - völlig kostenlos!
Verbinden Sie Ihr Team und Ihre Kunden Telefonie Livechat Videokonferenzen

Gehostet oder selbst-verwaltet. Für bis zu 10 Nutzer dauerhaft kostenlos. Keine Kreditkartendetails erforderlich. Ohne Risiko testen.

3CX
Für diese E-Mail-Adresse besteht bereits ein 3CX-Konto. Sie werden zum Kundenportal weitergeleitet, wo Sie sich anmelden oder Ihr Passwort zurücksetzen können, falls Sie dieses vergessen haben.