similar to: More on W6692pci NT mode under chan_misdn

Hi all, Does anybody of you have the winbond w6692 working with the mISDN/chan_misdn.so? When loading chan_misdn.so from Asterisk, I get a "No lower Id port:1" error. The /var/log/messages file says: "MISDN free_device: entitylist not empty" I'm using Linux 2.6.11.11 + mISDN-CVS-2005-05-01 + Asterisk 1.0.7 + Zaptel 1.0.7 chan_misdn build from chan_misdn-beta-0.0.3-rc6

Hello ! I would like to get working a Fritz PCI card using chan_misdn operating in ptp mode. Afer compiling mISDN into the kernel and building chan_misdn Asterisk stops loading with : [chan_misdn.so] => (Channel driver for mISDN Support (Bri/Pri)) == Parsing '/etc/asterisk/misdn.conf': Found UnLocking config_mutex == Registered channel type 'mISDN' (This driver enables

Has anyone got chan_misdn working with passive BRI cards yet? I've tried both hfc (hfcpci.ko) and w6692 (w6692pci.ko) cards, but when I start asterisk I get the following when chan_misdn is loaded: [chan_misdn.so] => (Channel driver for mISDN Support (Bri/Pri)) == Parsing '/etc/asterisk/misdn.conf': Found == Registered channel type 'mISDN' (This driver enables the

Hello It is all very confusing due to little information available :) I have a w6692 PCI card, so 1) What ports or modes i can use it? Currently i am plugged into a T0 port, can it be used? And what's the difference from S0? Please point me to some reading full of clues. 2) Due to lack of my understanding of the modes i can't seem to get the right protocol and layermask values for

hello, i have a problem on started asterisk, when try to start asterisk a get the fowlling error: chan_misdn.so] => (Channel driver for mISDN Support (Bri/Pri)) Feb 17 11:34:01 WARNING[3104]: config_old.c:27 ast_load: ast_load is deprecated, use ast_config_load instead! == Parsing '/etc/asterisk/misdn.conf': Found Feb 17 11:34:01 WARNING[3104]: config_old.c:39 ast_destroy: ast_destroy

I'm using avm fritz card usb with kernel 2.6 patch with mISDN. The module is load correctly when I type lsmod I've got the following output: Module Size Used by zaptel 178308 0 avmfritz 21388 0 mISDN_isac 14336 1 avmfritz mISDN_dsp 191424 0 l3udss1 34184 0 mISDN_l2 39040 0

Hi For use my isdn card in NT mode I have compiled chan_misdn. When I launch asterisk it stop with th e message : [chan_misdn.so] => (Channel driver for mISDN Support (Bri/Pri)) == Parsing '/etc/asterisk/misdn.conf': Found UnLocking config_mutex == Registered channel type 'mISDN' (This driver enables the asterisk to use hardware which is supported by the new ) Locking

Hi i am experiencing some problem with asterisk and misdn i've patched and recompiled the 2.6.15.5 kernel on the server i use a BN8S0 card with alla channels in TE mode. i can load hfcmulti and mISDN_dsp i load this with: /sbin/modprobe hfcmulti layermask=0xf protocol=0x22 type=0x08 and then /sbin/modprobe mISDN_dsp dmesg returns me the following: Modular ISDN Stack core $Revision: 1.34

hi i am experiencing some problems with the configuration of an BN8S0 Beronet card. I've downloaded last CVS of mISDN ans mISDNuser, i patch the kernel 2.6.16.18 and the enabled the following: <*> ISDN support x x Old ISDN4Linux ---> x x --- CAPI subsystem x x <M> CAPI2.0 support x x [*] Verbose reason code reporting (kernel size +=7K) x x [*]

Hi all! I'm getting an error when I try to start asterisk with chan_misdn. I patched my kernel (2.6.12.4), and compiled the whole stuff (kernel, mISDNuser, asterisk, chan_misdn). I got mISDN from http://isdn.jolly.de/download/v3.0/ I'm using a CVS Snapshot of asterisk, which was checked out about 5 hours ago. This is the error: [chan_misdn.so]Aug 15 14:13:29 WARNING[4929]:

Hi, I have a Digium B410P 4-port BRI card. I installed misdn 1.1.3 with hfcmulti driver and misdnuser 1.1.3. I configured the card "correctly" as misdnportinfo reports: # misdnportinfo Port 1: TE-mode BRI S/T interface line (for phone lines) -> Interface is Poin-To-Point. -> Protocol: DSS1 (Euro ISDN) -> childcnt: 2 -------- Port 2: TE-mode BRI S/T interface line (for

Hello List, I have got some questions about mISDN kernel buffer messages which I posted to the mISDN users list a while ago. Unfortunatelly I received no feedback at all, so I though I'd share them in this (wider) context to see if anyone can give any input... Thanks in advance for any feedback and kind regards, -- Ex Vito ---------- Forwarded message ---------- From: Ex

Hi List, I?m having problems compiling chan_misdn: asterisk:/usr/src/chan_misdn-beta-0.0.3-rc4 # make install cc -ggdb -Wall -D_GNU_SOURCE -Wno-missing-prototypes -Wno-missing-declarations -fPIC -I/usr/src/asterisk/include -DAST_CONFIG_DIR=\"/etc/asterisk/\" -I/usr/src/mISDNuser/include -I/usr/src/linux-2.6/include -I/usr/src/mISDNuser/i4lnet/ -Wall -c -o chan_misdn.o chan_misdn.c

Hello everyone. I've got a HFC ISDN card that I'm using with chan_misdn and it basically behaves like crap. Echo is waaay worst then echo I get TDM400 card, sound is "choppy" (there other side is allays complaining about sound interruptions) and to top it all it detects fake DTMF's all the time. Is this a chan_misdn problem or is it a card problem? I really need to get

Quick question: Is there a way to distinguish between calling MSN's when using chan_misdn? More info: I've got my ISDN2 (EuroISDN) up and running here in Romania with 1 base number plus 5 MSN's. Now I want to my * to do different things when receiving a call on from different MSN's (like forwarding the call to my FAX machine or forwarding the call to my mobile). The obvious way

What are the advantages in using mISDN over other solutions? If I knew why it was a good idea (like does it have better sound quality than alternatives?) then I would put the time in to test it, and also improve the Wiki. -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Thomas H?ger Sent: Friday, January 21,

Hi there, we've announced a new release of our chan_misdn channel driver. chan_misdn is a GPL channel driver for the new Linux ISDN-Layer mISDN (www.isdn4linux.org). So you can use all from mISDN supported ISDN catds in Asterisk. Feel free to donwload and test it at : http://www.beronet.com/download/chan_misdn-beta-0.0.3-rc4.tgz You can report bugs and feature requests to

Hi there, we've announced a new release of our chan_misdn channel driver. chan_misdn is a GPL channel driver for the new Linux ISDN-Layer mISDN (www.isdn4linux.org). So you can use all from mISDN supported ISDN catds in Asterisk. Feel free to donwload and test it at : http://www.beronet.com/download/chan_misdn-beta-0.0.3-rc5.tgz You can report bugs and feature requests to

Hi list, I installed a fresh Debian/Etch with Asterisk 1.4 and Zaptel 1.4 from SVN for 2 Digium B410P card. I ran configure in Asterisk dir, went in zaptel dir and: make, make install, make b410p. Everything is ok. Now I want to compile Asterisk but can't activate the chan_misdn channel which depends on -from menuselect- isdnnet(E), misdn(E), suppserv(E) When I made the make b410p, all

Could someone please comment on the current state of chan_capi, chan_misdn and chan_modem channel drivers in terms of functionality and stability. Specifically, which channel driver would be best for a passive PCI HFC or W6692 ISDN card. The chan_misdn wiki claims that chan_capi distinguishes between junghanns and non-junghans cards, and that chan_misdn is better suited for general misdn