similar to: chan_misdn and passive BRI cards

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

So far i've grasped that to use a card in NT mode it should have layermask=3 as module option. Is it the only thing that sets TE or NT mode for card? Perhaps there are settings in misdn.conf ? I can only get the card to work in TE mode and even then when asterisk is ran as asterisk -vvvgc it exits right after chan_misdn is loaded with theese messages: [chan_misdn.so] => (Channel driver

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

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

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

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

HI: Is there any way to raise up sound volume on fxo on TDM04B without changing tx-gain and rx-gain ? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Hi All, I'm trying to use a HFC chip ISDN modem with mISDN and chan_misdn. The card is configured to NT, PmP mode. One Siemens ISDN phone connected to the modem. When I call the ISDN phone is called everything is just fine, but when I call from the ISDN phone I face some problems. - There is no dial tone when I pick up the handset. - I call a number but there is no ringtone and after I

I have a ISDN BRI card with hisax module (w6692) and there is a lot of echo when I make calls to outside. Between the sip softphones the echo doesn't exist, but when I call to outside through the ISDN the echo exist. Is there any sense to put echocancellation in modem.conf ? ___________________________________________________ Nueva tecnología de Yahoo! Búsquedas ¿te atreves a comparar?

Hi Jon, perfect instructions, thank you very much. I used them and after some tests they worked. Here is what I did. Maybe someone could use it completely: ------------------------------------------------------------ Install helpers: apt-get install kernel-package ncurses-dev fakeroot wget bzip2 Go to usr directory: cd /usr/src wget

I can't find solution anywhere. I googled and find people with the same problem but there was no answers on how to fix this. I have W6692 based PCI cards that uses hisax driver (card type=36). Card is working fine under asterisk with i4l modem driver for incoming calls. If I want to dial out using some sip phone I don't get ring indication. Phone is ringing and I hear only silence until

From: Ben Skeggs <bskeggs at redhat.com> Because NVIF intentionally lacks some of the paths necessary to be compatible with various mistakes we've made over the years, libdrm needs to know whether a client has been updated and that it's safe to make use of the new kernel interfaces. Clients still using nouveau_device_open()/wrap() will be forced to make use of ABI16 instead of

From: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- nouveau/nouveau.c | 46 +++++++++++++++++++++------------------------- 1 file changed, 21 insertions(+), 25 deletions(-) diff --git a/nouveau/nouveau.c b/nouveau/nouveau.c index 9f82fde..e304a1b 100644 --- a/nouveau/nouveau.c +++ b/nouveau/nouveau.c @@ -244,39 +244,36 @@

The first two patches basically fix two warnings, and the last one avoid compiling the whole core in Syslinux with debug enabled by default that was accidently added in commit 72842b6 I presume. Hi Matt, Please consider pulling too. Paulo The following changes since commit 1f822f83b3d757c9a72f1eb99ebd723ee61e625b: Fix Makefile install targets (2012-07-04 11:21:19 +0100) are available in

Hi all I've only been working with Asterisk for a matter of days but have already grown into a big fan =) Much as I've managed to get internal calling working fine, I have a configuration running on an old PII-233 on RH9 with a (although not badged as is a) Dynalink IS64PH/Winbond W6692 PCI Card as /dev/ttyI0. The card works fine in minitel and dials out without a problem.. However try

Any updates .. On 3/18/20 18:04, Amit Kumar wrote: > > Hello, > > smbclient cannot create log file when log-basename is specified in > samba-master. > > ?????? -l|--log-basename=logdirectory > ?????????? Base directory name for log/debug files. The extension > ".progname" will > ?????????? be appended (e.g. log.smbclient, log.smbd, etc...). The log >

Hi i've installed this software: ******************** SOFTWARE mISDN-1_1_7 mISDNuser-1_1_7 Asterisk-1.4.15 ******************** SOFTWARE misdn is correctly loaded by misdn-inist start Here there is the misdn.conf (copied from an existing and working installation with Asterisk 1.2.x and one BN8S0) ******************** MISDN.CONF [general] misdn_init=/etc/misdn-init.conf debug=0 bridging=no

Have you got termination set correctly? I have a B410P working with 2 x NT and 2 x TE ports successfully. I had to turn the 100ohm termination on on the NT ports (even though I have them set as PTP in mISDN.conf). HTH -->> -----Original Message----- -->> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users- -->> bounces at lists.digium.com] On

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 tried to install asterisk and mISDN via http://www.asterisk.org/downloads/yum My machine is running with kernel-2.6.18-164.15.1.el5.i686 # grep kernel /var/log/yum.log Mar 21 16:09:28 Installed: kernel-2.6.18-164.15.1.el5.i686 Mar 21 16:09:42 Installed: kernel-devel-2.6.18-164.15.1.el5.i686 I've installed the following packages: # yum install asterisk16-misdn mISDN mISDNuser