B400P and BN1E1 on the same machine

Hello,

We are trying to use two cards on the same machine: an OpenVox B400P and a beronet BN1E1. Unfortunately when we plug both cards in the machine mISDN 1.1.8 (which comes with Elastix 1.5) cannot detect the OpenVox card. If we remove the BN1E1 then mISDN can detect the OpenVox card.

Some info:
misdn 1.1.8
asterisk 1.4.24.1

/etc/mISDN.conf:
<mISDNconf>
<module poll="128" debug="0" timer="no">hfcmulti</module>
<module debug="0" options="0">mISDN_dsp</module>
<devnode user="asterisk" group="asterisk" mode="660">mISDN</devnode>
<card type="BN1E1">
<port mode="te" link="ptp">1</port>
</card>
<card type="BN4S0">
<port mode="te" link="ptmp">1</port>
<port mode="te" link="ptmp">2</port>
<port mode="te" link="ptmp">3</port>
<port mode="te" link="ptmp">4</port>
</card>
</mISDNconf>


Thanks,
John

hello:
what you mean" the system can not detect the card", lspci can not see that? have you try to adjust the card ID, you must adjust the jumper for that, if there are tow cards in the system.
james.zhu

Thanks for the quick reply! Your answers are most welcomed!

By that I meant that lspci shows both of the cards:
01:00.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-E1] (rev 01)
01:01.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)

I think I have found the problem. It seems that the problem is with mISDN. The beronet card is been recognized as BN1E1 (which it is) but mISDN 1.1.8 (which comes with elastix) does not have provision for BN1E1 (only for BN2E1). So the card is skipped in the hfcmulti line:

>> /sbin/modprobe --ignore-install hfcmulti type=0x4 protocol=0x2,0x2,0x2,0x2 layermask=0xf,0xf,0xf,0xf poll=128 debug=0 timer=0

which explains why one card is loaded only (the first one initialized). I cannot understand why the misdn.org project has dropped support for BN1E1. The correct one should be:

>> /sbin/modprobe --ignore-install hfcmulti type=0x1,0x4 protocol=0x22,0x2,0x2,0x2,0x2 layermask=0xf,0xf,0xf,0xf,0xf poll=128 debug=0 timer=0

Which apparently works as it can be seen from the logs:

Modular ISDN Stack core version (1_1_9.1) revision ($Revision: 1.40 $)
mISDNd: kernel daemon started (current:e6469550)
mISDNd: test event done
ISDN L1 driver version 1.20
ISDN L2 driver version 1.32
mISDN: DSS1 Rev. 1.47
mISDN Capi 2.0 driver file version 1.21
mISDN: HFC-multi driver Rev. 1.68
hfcpci_probe: PROTOCOL turn on CRC4 report: card(1) port(0)
HFC-multi: card manufacturer: 'Cologne Chip AG' card name: 'HFC-E1 Beronet Card' clock: normal
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 21 (level, low) -> IRQ 217
HFC-E1#1: defined at IOBASE 0xbc00 IRQ 217 HZ 1000 leds-type 1
HFC_multi: resetting HFC with chip ID=0xe revision=1
register_layer: register_sysfs failed -17 st(00000100) inst(40000100)
HFC-multi: card manufacturer: 'Cologne Chip AG' card name: 'HFC-4S OpenVox Card' clock: double
PCI: Enabling device 0000:01:01.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 209
HFC-4S#2: defined at IOBASE 0xb800 IRQ 209 HZ 1000 leds-type 2
HFC_multi: resetting HFC with chip ID=0xc revision=1
hfcpci_probe: DIPs(0x4) jumpers(0x0)
register_layer: register_sysfs failed -17 st(00000200) inst(40000200)
register_layer: register_sysfs failed -17 st(00000300) inst(40000300)
register_layer: register_sysfs failed -17 st(00000400) inst(40000400)
register_layer: register_sysfs failed -17 st(00000500) inst(40000500)
2 devices registered
mISDN_dsp: Audio DSP Rev. 1.29 (debug=0x0) EchoCancellor MG2 dtmfthreshold(100)
mISDN_dsp: DSP clocks every 64 samples. This equals 8 jiffies.

By the way should I be concerned by that "failed -17" errors?

Thanks.

hello,
I do not think it will work without worry. you have to check the that! do you have any modules(hisax) connecting with mISDN? make sure remove hisax!
regards!
James.zhu

Original posted by james.zhu at 2009-5-20 20:33

hello,
I do not think it will work without worry. you have to check the that! do you have any modules(hisax) connecting with mISDN? make sure remove hisax!
regards!
James.zhu

Thanks for the info..By the way,I'm not that techie. Would you mind telling me what the meaning of hisax?
Thanks!

Regards,
sallyhawks
Disque dur multimedia

hello
HiSax is a Linux hardware-level driver for passive ISDN cards with Siemens
chipset (ISAC_S 2085/2086/2186, HSCX SAB 82525).
it is an old driver which conflicts with our driver, please just do as james said