keywords: ip pbx voip gateway gsm gateway

×

Notice

The forum is in read only mode.
× Questions about B100/200/400/800 ISDN BRI Cards

2xA1200P + B400P - a few problems...

15 years 6 months ago #2212 by vmiro
My configuration:
A1200P (zaptel driver)
A1200P (zaptel driver)
B400P (mISDN + SoftEcho)

Asterisk 1.4.22
Zaptel 1.4.11

1. I'm having problems with misdn-init startup script. It shows that mISDN necessary modules are loaded, but when I use 'misdnportinfo' command to check the channels, I get errors like "There is no card...". Log:

Nov 20 19:49:39 astelektron kernel: octvqe: OCTVQE-MOD-01.03.00-PR. Using major 254, Default EC "MG2" (Built on Nov 20 2008 16:34:31).
Nov 20 19:49:39 astelektron kernel: ISDN L1 driver version 1.20
Nov 20 19:49:39 astelektron kernel: ISDN L2 driver version 1.32
Nov 20 19:49:39 astelektron kernel: mISDN: DSS1 Rev. 1.47
Nov 20 19:49:39 astelektron kernel: mISDN_dsp: no version for "ZapOctVqeApiEcChannelTrainTap" found: kernel tainted.
Nov 20 19:49:39 astelektron kernel: mISDN_dsp: Audio DSP Rev. 1.29 (debug=0x0) EchoCancellor octasic dtmfthreshold(100)
Nov 20 19:49:39 astelektron kernel: mISDN_dsp: DSP clocks every 128 samples. This equals 16 jiffies.


After I restart misdn module (misdn-init restart), 'misdnportinfo' shows configured ISDN channels and the misdn channels are available in Asterisk. Log:

Nov 20 19:50:18 astelektron kernel: octvqe: Echo cancellation support unloaded
Nov 20 19:50:20 astelektron kernel: octvqe: OCTVQE-MOD-01.03.00-PR. Using major 254, Default EC "MG2" (Built on Nov 20 2008 16:34:31).
Nov 20 19:50:20 astelektron kernel: Modular ISDN Stack core version (1_1_8-OCT) revision ($Revision: 1.40 $)
Nov 20 19:50:20 astelektron kernel: ISDN L1 driver version 1.20
Nov 20 19:50:20 astelektron kernel: ISDN L2 driver version 1.32
Nov 20 19:50:20 astelektron kernel: mISDN: DSS1 Rev. 1.47
Nov 20 19:50:20 astelektron kernel: mISDN: HFC-multi driver Rev. 1.68
Nov 20 19:50:20 astelektron kernel: HFC-multi: card manufacturer: 'Cologne Chip AG' card name: 'HFC-4S OpenVox Card' clock: double
Nov 20 19:50:20 astelektron kernel: ACPI: PCI Interrupt 0000:0c:02.0[A] -> GSI 26 (level, low) -> IRQ 193
Nov 20 19:50:20 astelektron kernel: HFC-4S#1: defined at IOBASE 0x4400 IRQ 193 HZ 1000 leds-type 2
Nov 20 19:50:20 astelektron kernel: HFC_multi: resetting HFC with chip ID=0xc revision=1
Nov 20 19:50:20 astelektron kernel: hfcpci_probe: DIPs(0x7) jumpers(0x0)
Nov 20 19:50:21 astelektron kernel: 1 devices registered
Nov 20 19:50:21 astelektron kernel: mISDN_dsp: Audio DSP Rev. 1.29 (debug=0x0) EchoCancellor octasic dtmfthreshold(100)

So, everything works but the problem is with starting the misdn modules when boot.

Line...
Nov 20 19:49:39 astelektron kernel: mISDN_dsp: no version for "ZapOctVqeApiEcChannelTrainTap" found: kernel tainted.
...is kinda problem?!


2. I've read some posts here on forum about "buffer re-sync occur..." message. I got these messages when loading card drivers. Can it be ignored? I need to put this system in production and I don't want to happen something bad :|


Thanks ;)
15 years 6 months ago #2214 by james.zhu
hello:
please check that:
1) if you use misdn-init you have to edit the file to detect the card. please refer user manual
2) if the message appears once or two times, ignore that.
regards!
james.zhu

15 years 6 months ago #2219 by vmiro
misdn conf files are configured properly, but the problem is that I need to start misdn-init script twice for the card to be recognized. First time the misdn-init script starts during boot (chkconfig) and the second I do it manually (misdn-init restart).
15 years 6 months ago #2247 by vmiro
I'm getting the following message in my log file every time I make or receive call over mISDN channel:

Debug: sleeping function called from invalid context at mm/slab.c:2063
in_atomic():0[expected: 0], irqs_disabled():1
[<c0120289>] __might_sleep+0x7d/0x88
[<c0148cbf>] kmem_cache_alloc+0x1d/0x57
[<e0bce6dd>] bchdev_echocancel_activate+0x80/0x25e [mISDN_dsp]
[<e0bce5f7>] dsp_cancel_init+0x91/0xa0 [mISDN_dsp]
[<e0bc84e8>] dsp_control_req+0x4c2/0x67d [mISDN_dsp]
[<e0bc88a6>] dsp_from_up+0x202/0x2f2 [mISDN_dsp]
[<e0bc8fed>] dsp_function+0x2a/0x35 [mISDN_dsp]
[<e0a7ee5a>] mISDNStackd+0x325/0x56a [mISDN_core]
[<c0120559>] autoremove_wake_function+0x0/0x2d
[<c02e099e>] ret_from_fork+0x6/0x14
[<c0120559>] autoremove_wake_function+0x0/0x2d
[<e0a7eb35>] mISDNStackd+0x0/0x56a [mISDN_core]
[<c01041f5>] kernel_thread_helper+0x5/0xb

Is it normal or....?
It happens on my two asterisk systems. One is working ok (with B100P), but the one I'm working with now is unstable so I'm wondering is it maybe related with those messages?!
15 years 5 months ago #2254 by vmiro
Anyone ??
15 years 5 months ago #2255 by miaolin
do not meet this bug before, but it looks like something wrong with the mISDN device driver, maybe due to linux kernel imcompatible or bad linux kernel source or you have to compile mISDN again.

what linux you are using?
Time to create page: 0.040 seconds
Powered by Kunena Forum