search for: capidrv

...03 #0x0003 LEN=0014 Controller/PLCI/NCCI = 0x101 Reason = 0x3302 == DISCONNECT_IND PLCI=0x101 REASON=0x3302 == Spawn extension (OutDial-Dial, h, 1) exited non-zero on 'SIP/ePfd-7515' dmesg shows: isdn_dc2minor: di(0) ch(-1072539760) invalid capidrv-1: now up (2 B channels) capidrv-1: D2 trace enabled capi: controller 1 up kcapi: notify up contr 2 capidrv: controller 2 up isdn_dc2minor: di(1) ch(-1072539760) invalid capidrv-2: now up (2 B channels) capidrv-2: D2 trace enabled capi: controller 2 up kcapi: notify up contr 3 capidrv: controller 3...

...? On the voip-info.org Wiki is only notice to: You will need a section for each controller in /etc/asterisk/capi.conf so the C2 will have 2 sections. But how is look like this ? Only on the first port is asterisk assume connections, but nothing on the second card port. In the dmesg is only the capidrv-1 shown, no capidrv-2, only the isdnlog is shown the incoming call on the second port. Has anyone an usable (capi.conf?) configration ? Thx in advanced and regards, Andreas. -- appendix -- capidrv: Rev 1.1.2.2: loaded b1: revision 1.1.2.2 ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 5 (le...

...st curious about this failure? The serious problem is that asterisk no longer answers calls: they are seen by isdn_net and isdn_tty but even if ignored are not passed to asterisk for further processing. Is there a way to have i4l attach only to one controller on the 4BRI? - if I load the capidrv module, at first it seems to work: Apr 25 08:08:19 zenon kernel: capidrv-1: now up (2 B channels) Apr 25 08:08:19 zenon kernel: capidrv-1: not from AVM, no d-channel trace possible (Eicon Networks) [same message for controllers 2,3,4] then after a few seconds I get these errors: Apr 25 08:1...

...:06:31 * Call to tei 127 from 01722950xxx on 30 HLC: CCITT, Telefonie Jan 20 10:06:31 server capifaxrcvd[1062]: Incoming Call from 01722950xxx Jan 20 10:06:31 server capifaxrcvd[1062]: C30d #: 30 Jan 20 10:06:31 server capifaxrcvd[1062]: Call from 01722950xxx ignored Jan 20 10:06:31 server kernel: capidrv-1: incoming call 01722950xxx,1,1,30 Jan 20 10:06:31 server kernel: capidrv-1: patching si2=1 to 0 for VBOX Jan 20 10:06:31 server kernel: isdn_net: call from 01722950xxx,1,0 -> 30 Jan 20 10:06:31 server kernel: isdn_net: call from 01722950xxx -> 0 30 ignored Jan 20 10:06:31 server kernel: isd...

...ers, however there is an error message: FAC REQ - Illegal application number (0x1101) - capi2i4l (compatibility with isdn4linux) works fine: I can use ipppd, and dial into the server with minicom, - here is the "lsmod" output: Module Size Used by Tainted: P capidrv 26740 8 isdn 103136 1 [capidrv] capi 18048 0 divacapi 161884 -28 kernelcapi 30368 -18 [capidrv capi divacapi] capiutil 22912 0 [capidrv kernelcapi] diva_idi 15592 0 divas...

..._deflate 4640 0 zlib_deflate 21784 1 ppp_deflate zlib_inflate 21280 1 ppp_deflate bsd_comp 5280 0 ppp_synctty 7712 1 ppp_generic 22516 8 ppp_async,ppp_deflate,bsd_comp,ppp_synctty slhc 6368 1 ppp_generic capidrv 30036 1 isdn 110464 1 capidrv capi 16416 6 capifs 3912 2 capi cmtp 16896 3 kernelcapi 43584 3 capidrv,capi,cmtp l2cap 21540 3 cmtp snd_pcm_oss 50724 0 snd_pcm...

Hello, I'm trying to install CAPI Driver for Suse 9.2 and I found the documentation for this pretty old since It refers to Suse 8.2 ( http://www.voip-info.org/wiki-Asterisk+AVM+Fritz+CAPI+Driver+Install ). This is especially apparent when I look at the section of these instructions for altering "src.drv/makefile" to replace the occurance of "CARD_PATH". I tried to

I have an asterisk installation connected to 2 isdn lines via an AVM C2 card. modules seems to load well, lsmod gives : c4 19588 4 b1 24192 1 c4 capidrv 28468 2 isdn 134604 9 capidrv slhc 7552 1 isdn capi 18112 4 capifs 6024 2 capi kernelcapi 46112 4 c4,b1,capidrv,capi 'capi info' from * console returns correctly : Contr1: 2 B channels...

...s some idea? Note: Asterisk without the QuadBRI module and chan_capi is working well, but I have compiled it with explicit PROC=i386, because 'uname -m' returns i686, but the VIA processor does not support some of 686 instructions that the Asterisk executable uses. # lsmod | grep capi capidrv 29748 0 isdn 128204 1 capidrv capi 17728 0 capifs 6024 2 capi kernelcapi 46624 6 c4,blpci,bldma,bl,capidrv,capi

...trying to setup a AVM C2 card. I have read the kernel requirements for this card. <M> CAPI2.0 support [*] Verbose reason code reporting (Kernel size +=7K) [*] CAPI2.0 Middleware support (EXPERIMENTAL) <M> CAPI2.0 /dev/capi support [*] CAPI2.0 filesystem support <M> CAPI2.0 capidrv interface support My problem is when I make a "make menuconfig" in /usr/src/linux/, i can't see any reference to CAPI2.0 filesystem support, in my kernel, 2.4.18 (Debian stable). When I make a capiinit, to test the AVM card, it says, debian-asterisk:~# capiinit modprobe: Can...

I tried that but it still doesn't work... I think I don't have the correct approach. Have I to install any ISDN drivers (=modules ?) BEFORE dealing with CAPI ? If yes, why shouldn't I use the hisax drivers (which are kernel ones) instead of fcpci drivers (which doesn't seems to work, by the way...) And finally, how is it possible to link the two modules together? As you can see,

...6912 1 capability af_packet 21384 2 ipv6 233344 27 ext3 120200 1 jbd 53524 1 ext3 via_velocity 30752 0 r8169 25736 0 capi 17216 0 capifs 5768 2 capi capidrv 28340 0 kernelcapi 45472 2 capi,capidrv ide_disk 16256 0 psmouse 33028 0 joydev 9152 0 snd_via82xx 26648 0 gameport 15112 1 snd_via82xx evdev 9088 0 snd_ac97_codec 831...

...s1,mISDN_l2,mISDN_l1 edd 9240 0 joydev 10304 0 sg 35488 0 st 39196 0 sr_mod 16292 0 ide_cd 36740 0 cdrom 36892 2 sr_mod,ide_cd nvram 8456 0 capidrv 28340 0 isdn 134092 1 capidrv slhc 7552 1 isdn capi 17728 0 capifs 5896 2 capi kernelcapi 45856 2 capidrv,capi usbserial 29040 0 parport_pc 35392 1 lp...

One of my buddies signed up with GV yesterday with a view to using them on his * server. Problem is that the settings they gave him don't work with asterisk. They do however work with X-Lite. Any ideas? He's using the settings outlined on my web page. Mark -- Mark, G7LTT/KC2ENI Randolph, NJ http://www.g7ltt.com

Hi All, Has anyone had success with using the AVM Fritz PCI ISDN Card (v2) CAPI drivers with a distro other than suse? The AVM driver is geared towards suse, and after trying them with RedHat 9 I've not got very far. The module compiles but dies when I attempt to modprobe it. I've googled until I almost lost the will to live! What little information I can find seems to refer back to

Any ideas on the following? (CVS 10/01/2003) Only reference I could find was a Zaptel change log update... 2003-09-02 18:23 martinp * wct4xxp.c (1.6): Get rid of the Double missed interrupt message every time you load the driver and an email refering this to serial console usage. Something I should worry about? Oct 3 22:48:01 cti-350 kernel: TE410P: Double/missed interrupt detected Oct 3

...N support --- CAPI subsystem <M> CAPI2.0 support [ ] Verbose reason code reporting (kernel size +=7K) [*] CAPI2.0 Middleware support (EXPERIMENTAL) <M> CAPI2.0 /dev/capi support [*] CAPI2.0 filesystem support < > CAPI2.0 capidrv interface support --- CAPI hardware drivers Active AVM cards ---> Active Eicon DIVA Server cards ---> Modular ISDN driver ---> <M> Support modular ISDN driver [ ] Enable memory leak debug for mISDN (NEW) [*] Support for AVM Fritz!...

...edly). #!/bin/sh if [ $# -ge 1 ]; then DEBUG=$1 else DEBUG=0 fi if [ $# -ge 2 ]; then DEBUG_F=$2 else DEBUG_F=0xffffffff fi if [ $# -ge 3 ]; then ttt=$3 else ttt=180 fi #INSMOD_PARA=-m MEXT=.ko cd /usr/src/linux/drivers/isdn/hardware/mISDN #modprobe capidrv modprobe capi insmod ${INSMOD_PARA} mISDN_core${MEXT} debug=${DEBUG} >/tmp/m_core.mod # insmod ${INSMOD_PARA} faxl3${MEXT} debug=${DEBUG_F} ttt=$ttt > /tmp/m_faxl3.mod insmod ${INSMOD_PARA} mISDN_l1${MEXT} debug=${DEBUG} >/tmp/m_l1.mod insmod ${INSMOD_PARA} mISDN_l2${MEXT} debug=${DEBUG}...

Hi everyone, i''m currently try migrate my mythtv-server into an xen maschine but the ivtv-driver for my Hauppauge PVR350 doesn''t work. Now, a lot of googling and reading later i''m now here. I''ve an error which i can''t exactly allocate: is it an driver or an xen generated error ? I got with the ivtv-drivers following error: (0.2.x ivtv driver)