We are trying to get our first B410P installation working but unable to get any L1 or L2 links. Connecting 3 ports to BRI lines via S/T interfaces on telco provided NT equipment. Using Debian etch 2.6.18-6 Ports are configured as TE Have tried both PTP and PTMP modes All 4 red lights are flashing. When we connect the ISDN cable, NOTHING HAPPENS and unable to receive or make calls. Have tried both Cross-over and straight through cables. Telco is adamant the ISDN lines are working fine. # misdn-init scan [OK] found the following devices: card=1,0x4 # misdnportinfo Port 1: TE-mode BRI S/T interface line (for phone lines) -> Interface is Poin-To-Point. -> Protocol: DSS1 (Euro ISDN) -> Layer 4 protocol 0x04000001 is detected, but not allowed for TE lib. -> childcnt: 2 * Port NOT useable for PBX (maybe there is already a PBX running?) .... and so on The driver appears to load OK, except for some entries highlighted below. Syslog from starting the driver: May 23 22:27:22 cats kernel: Modular ISDN Stack core version (1_1_7_2) revision ($Revision: 1.40 $) May 23 22:27:22 cats kernel: mISDNd: kernel daemon started (current:c8ac7030) May 23 22:27:22 cats kernel: mISDNd: test event done May 23 22:27:22 cats kernel: ISDN L1 driver version 1.20 May 23 22:27:22 cats kernel: ISDN L2 driver version 1.32 May 23 22:27:22 cats kernel: mISDN: DSS1 Rev. 1.47 May 23 22:27:22 cats kernel: mISDN Capi 2.0 driver file version 1.21 May 23 22:27:23 cats kernel: mISDN: HFC-multi driver Rev. 1.68 May 23 22:27:23 cats kernel: HFC-multi: card manufacturer: 'Cologne Chip AG' card name: 'HFC-4S Digium Card' clock: normal May 23 22:27:23 cats kernel: PCI: Enabling device 0000:00:0c.0 (0000 -> 0003) May 23 22:27:23 cats kernel: ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 17 (level, low) -> IRQ 193 May 23 22:27:23 cats kernel: HFC-4S#1: defined at IOBASE 0xff00 IRQ 193 HZ 250 leds-type 2 May 23 22:27:23 cats kernel: HFC_multi: resetting HFC with chip ID=0xc revision=1 May 23 22:27:23 cats kernel: Setting GPIOs May 23 22:27:23 cats kernel: calling vpm_init May 23 22:27:23 cats kernel: VPM: Chip 0: ver 33 May 23 22:27:23 cats kernel: VPM: A-law mode May 23 22:27:23 cats kernel: VPM reg 0x20 is 11 May 23 22:27:23 cats kernel: NLP Thresh is set to 2 (0x2) May 23 22:27:23 cats kernel: VPM: A-law mode May 23 22:27:23 cats kernel: VPM reg 0x20 is 11 May 23 22:27:23 cats kernel: NLP Thresh is set to 2 (0x2) May 23 22:27:23 cats kernel: hfcpci_probe: DIPs(0x90) jumpers(0x0) May 23 22:27:23 cats kernel: register_layer: register_sysfs failed -17 st(00000100) inst(40000100) ?======= Bothered by these entries May 23 22:27:23 cats kernel: register_layer: register_sysfs failed -17 st(00000200) inst(40000200) May 23 22:27:23 cats kernel: register_layer: register_sysfs failed -17 st(00000300) inst(40000300) May 23 22:27:24 cats kernel: register_layer: register_sysfs failed -17 st(00000400) inst(40000400) May 23 22:27:24 cats kernel: 1 devices registered May 23 22:27:24 cats kernel: mISDN_dsp: Audio DSP Rev. 1.29 (debug=0x0) EchoCancellor MG2 dtmfthreshold(100) May 23 22:27:24 cats kernel: mISDN_dsp: DSP clocks every 128 samples. This equals 4 jiffies. CLI> misdn show stacks BEGIN STACK_LIST: * Port 1 Type TE Prot. PTP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0 * Port 2 Type TE Prot. PTP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0 * Port 3 Type TE Prot. PTP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0 CLI> As usual its rather urgent to get it running. If anyone can provide suggestions ,I?d be very grateful. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080523/21c45fbe/attachment.htm
On Fri, May 23, 2008 at 8:41 AM, Chris Curtis <Chris.Curtis at cubemicrosystems.com> wrote:> We are trying to get our first B410P installation working but unable to get > any L1 or L2 links. > > Connecting 3 ports to BRI lines via S/T interfaces on telco provided NT > equipment. > > > > Using Debian etch 2.6.18-6 > > > > Ports are configured as TE > > Have tried both PTP and PTMP modes > > > > All 4 red lights are flashing. When we connect the ISDN cable, NOTHING > HAPPENS and unable to receive or make calls. > > Have tried both Cross-over and straight through cables. > > Telco is adamant the ISDN lines are working fine. > > > > # misdn-init scan > > [OK] found the following devices: > > card=1,0x4 > > > > # misdnportinfo > > > > Port 1: TE-mode BRI S/T interface line (for phone lines) > > -> Interface is Poin-To-Point. > > -> Protocol: DSS1 (Euro ISDN) > > -> Layer 4 protocol 0x04000001 is detected, but not allowed for TE lib. > > -> childcnt: 2 > > * Port NOT useable for PBX (maybe there is already a PBX running?) > > > > .... and so on > > > > The driver appears to load OK, except for some entries highlighted below. > > Syslog from starting the driver: > > > > May 23 22:27:22 cats kernel: Modular ISDN Stack core version (1_1_7_2) > revision ($Revision: 1.40 $) > > May 23 22:27:22 cats kernel: mISDNd: kernel daemon started > (current:c8ac7030) > > May 23 22:27:22 cats kernel: mISDNd: test event done > > May 23 22:27:22 cats kernel: ISDN L1 driver version 1.20 > > May 23 22:27:22 cats kernel: ISDN L2 driver version 1.32 > > May 23 22:27:22 cats kernel: mISDN: DSS1 Rev. 1.47 > > May 23 22:27:22 cats kernel: mISDN Capi 2.0 driver file version 1.21 > > May 23 22:27:23 cats kernel: mISDN: HFC-multi driver Rev. 1.68 > > May 23 22:27:23 cats kernel: HFC-multi: card manufacturer: 'Cologne Chip AG' > card name: 'HFC-4S Digium Card' clock: normal > > May 23 22:27:23 cats kernel: PCI: Enabling device 0000:00:0c.0 (0000 -> > 0003) > > May 23 22:27:23 cats kernel: ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 17 > (level, low) -> IRQ 193 > > May 23 22:27:23 cats kernel: HFC-4S#1: defined at IOBASE 0xff00 IRQ 193 HZ > 250 leds-type 2 > > May 23 22:27:23 cats kernel: HFC_multi: resetting HFC with chip ID=0xc > revision=1 > > May 23 22:27:23 cats kernel: Setting GPIOs > > May 23 22:27:23 cats kernel: calling vpm_init > > May 23 22:27:23 cats kernel: VPM: Chip 0: ver 33 > > May 23 22:27:23 cats kernel: VPM: A-law mode > > May 23 22:27:23 cats kernel: VPM reg 0x20 is 11 > > May 23 22:27:23 cats kernel: NLP Thresh is set to 2 (0x2) > > May 23 22:27:23 cats kernel: VPM: A-law mode > > May 23 22:27:23 cats kernel: VPM reg 0x20 is 11 > > May 23 22:27:23 cats kernel: NLP Thresh is set to 2 (0x2) > > May 23 22:27:23 cats kernel: hfcpci_probe: DIPs(0x90) jumpers(0x0) > > May 23 22:27:23 cats kernel: register_layer: register_sysfs failed -17 > st(00000100) inst(40000100) ?======= Bothered by these entries > > May 23 22:27:23 cats kernel: register_layer: register_sysfs failed -17 > st(00000200) inst(40000200) > > May 23 22:27:23 cats kernel: register_layer: register_sysfs failed -17 > st(00000300) inst(40000300) > > May 23 22:27:24 cats kernel: register_layer: register_sysfs failed -17 > st(00000400) inst(40000400) > > May 23 22:27:24 cats kernel: 1 devices registered > > May 23 22:27:24 cats kernel: mISDN_dsp: Audio DSP Rev. 1.29 (debug=0x0) > EchoCancellor MG2 dtmfthreshold(100) > > May 23 22:27:24 cats kernel: mISDN_dsp: DSP clocks every 128 samples. This > equals 4 jiffies. > > > > CLI> misdn show stacks > > BEGIN STACK_LIST: > > * Port 1 Type TE Prot. PTP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0 > > * Port 2 Type TE Prot. PTP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0 > > * Port 3 Type TE Prot. PTP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0 > > CLI> > > > > As usual its rather urgent to get it running. If anyone can provide > suggestions ,I'd be very grateful. > > > > Chris >Is your card compatible with BRIStuff? Thanks, Steve Totaro
On Fri, 2008-05-23 at 22:41 +1000, Chris Curtis wrote:> We are trying to get our first B410P installation working but unable > to get any L1 or L2 links.Which mISDN and kernel version are you using? There was a problem with very recent kernels & mISDN so you might want to check the mISDN mailing list archives[1]. If your kernel version is 2.6.25 or newer than mISDN 1.1.7.2 will not work and you will need to install mISDN from git cause Christian committed some fixes[2]. ?The card does come with support from Digium. Have you tried calling them? Regards, Patrick [1] https://www.isdn4linux.de/mailman/listinfo/isdn4linux [2] http://www.isdn4linux.de/pipermail/isdn4linux/2008-May/003441.html