similar to: Fwd: Re: chan_misdn 0.0.3-rc5 - new release ! Please test it.

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-rc5.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-rc4.tgz You can report bugs and feature requests to

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 everybody, we've implemented a new Channel Driver for *. It uses the new mISDN isdn4linux architecture and supports bri te and nt mode for now. I assume, there are lots of bugs we didn't found yet, and even mISDN is rarely stable. So we search brave volunteers to test the driver. Get it at: http://www.beronet.com/?PageID=3017 There you can find also a new *-Application which

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

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 guess I'd need to run Beronet quad and octo bri cards under bristuff to get zaptel features (echo canceling, timing source).... Am I right or could I achieve this also with chan_misdn - their native driver ? Running bristuff on Beronet cards is unsupported. Has anyone succesfully run Beronet quad BRI cards under bristuff recently ? Do they work ? Regards, Rob.

Rafael J. Risco G.V. wrote: > > On Sat, 11 Dec 2004 16:49:12 +0000, Corvin <corvin.dun@wp.pl> wrote: >> Dnia sobota, 11 grudnia 2004 15:32, Rodolfo Grave napisa?: >> > Hi. >> > >> > I need to set up H323 on an Asterisk box. I've succesfuly compiled the >> > asterisk oh323 (including of course all the dependencies: PWlib and >> >

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 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

Hi everyone! I have very simple question, how to limit SIP phone user making calls to for example longdistant calls? Maybe: Put in his context in sip.conf context which don't provide possibility to make such calls? Is it correct? thanks for any help, regards, Corvin

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

> On Sat, 27 Nov 2004 19:37:54 +0000, Corvin <corvin.dun@wp.pl> wrote: > > I have very simple question, how to limit SIP phone user making > > calls to for example longdistant calls? > > This is how I do it - Thank you very much to all of you. I have one more question which troubles me. We have scenario: (only SIP is considered now) Subscriber A registered in Asterisk

Hi all, I can see huge traffic here over 400 post in 4 days. My proposal is to create asterisk newsgrup proposal or phpBB forum what do think about it ? BR, Corvin btw. I'm admin of phpBB Forum (slackware forum - polish language), nearly 900 users. I think if someone will prepare it good it can be great project. (but I have 7 person team).

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

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

Hi i am upgrading an asterisk server from 1.2.4 to 1.4. i've installed libpri 1.4 i've installed zaptel 1.4 I've installed the new version of misdn with the script of beronet. i use this configure script: ./configure --with-postgres=/usr/local/pgsql then: make menuselect [*] 1. cdr_csv [*] 2. cdr_custom [*] 3. cdr_manager XXX 4. cdr_odbc [*] 5. cdr_pgsql XXX 6. cdr_radius

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

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