similar to: Anyone using National ISDN (NI-1) BRI under Linux?

The card is an ASUSCOM ISDNLink PCI (passive) and the circuit is from Qwest (in the US). I will be using this circuit only for voice (I'm doing this because of the poor quality of my POTS lines). I've compiled Hisax (as a module) into my 2.4.25 kernel, and with 'modprobe hisax type=35 protocol=4 id=hisax' I get the following: Apr 7 10:34:24 dev kernel: HiSax: Linux Driver for

Hi After modprobe hisax type=35 (Billion HFC PCI) on a Xorcom Rapid ISO I get: HISAX Dec 12 16:25:35 localhost kernel: HiSax: Linux Driver for passive ISDN cards Dec 12 16:25:35 localhost kernel: HiSax: Version 3.5 (module) Dec 12 16:25:35 localhost kernel: HiSax: Layer1 Revision 1.1.4.1 Dec 12 16:25:35 localhost kernel: HiSax: Layer2 Revision 1.1.4.1 Dec 12 16:25:35 localhost kernel: HiSax:

Hi all, I'm new to asterisk and not too knowledgeable on ISDN, so please be gentle :) I have a dual-channel Eicon Diehl Diva card in a Debian Woody box with kernel 2.4.27, connecting to a Telstra (Australia) Onramp Home Highway ISDN line. I'm pretty certain the card and line both work since they've been used in this machine for PPP before this (but with an older kernel with DoV

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

Can anyone work out why my callerid doesn't work on my isdn4Linux with asterisk (or without asterisk for that matter)... This used to work fine, and I am quite confident that the telco is sending callerid information (because they always do on all ISDN lines standard, only extra cost on POTS lines). This is the information from dmesg, whether asterisk is running or not: isdn_net: Incoming

----- Original Message ----- From: Karl Heyes <karl@pts.tele2.co.uk> To: <icecast@xiph.org> Sent: Friday, January 31, 2003 5:29 PM Subject: Re: [icecast] Re: Compiling ices <p>> On Fri, 2003-01-31 at 06:39, Marc Remijn wrote: > ... > > > Kernel output: > > > > invalid operand: 0000 > > CPU: 0 > > EIP: 0010:[<d08e25b1>]

Hi, I'm in the process of setting up Asterisk in a SOHO environment using ISDN for trunking. More specifically a BRI 2B+D circuit where one SPID is used for the business and the other is used for personal. The circuit already exists, but is presently being interfaced to POTS phones via a TA. This configuration is not very common in the US, but we are fortunate that our LEC offers it price

I'm looking to use Asterisk with Verizon ISDN centex service in the US. I'd be connecting to an NT1 so I'd need an S/T interface. Users would have SIP phones registered with Asterisk and sharing the ISDN lines. The only PCI ISDN card that will support ISDN signalling in the US seems to be the Eicon Diva Server cards. These are hard to find and very expensive ($2500 for the Quad

I have asterisk loaded and seemingly working with 4 snom 200 phones. I cannot dial in or out using a DIVA isdn card When I dial out i get "not found xxxxxxx" on the handset. When I dial in i see in /var/log/message isdn_net: Incoming call without OAD, assuming '0' isdn_net: call from 0 -> 0 1856 ignored isdn_tty: Incoming call without OAD, assuming '0' isdn_tty:

Hello All, Has anyone configured bri to answer for only one msn? In essence, when the primary is busy I want to have channel 2 ring. I am using an eicon diva server bri I know I saw it in the windows interface, but don't see it in the linux setup. Regards, Greg

Hi, I am using Asterisk on a DSS1 ISDN-BRI with ISDN4Linux (and a Fritz Card PnP). The ISDN-BRI is in PTP-Mode (Point to Point "german: Anlagenanschluss") which is enabled within I4L with "hisaxctrl fcpcipnp0 7 1". Everything works fine except that I can not see the called number/MSN of incoming calls within Asterisk and because of this I can not route incoming calls

I have a zone "rw" defined as tun0 in interfaces. From that zone, pings to zone "loc" succeed but pings to remote networks (On IPsec VPNs) are rejected in the all2all chain. From my point of view, these pings should be in the rw2cctc chain. (rw to cctc is ACCEPTed in policy.) I must have a hole in my config, where would it be? Thanks, A.

Dear Shorewall Users :-) I''ve been playing with shorewall for some time now - I found it really interesting and easy tool to organise all the rules and so on (beforethat I''ve been using simple iptables rules in shell script ;-) Generally it''s quite easy to be used, but anyway found one problem which I cannot handle myself - or in other words - cannot find appropriate

Hi, I have written a package that contains many s4 generic functions and associated methods. I am having a lot of trouble getting R to build the help pages for these generic functions without reporting, "missing link(s): ~~fun~~, which means that it cannot find the appropriate function when code in the example section of the help is run. Right? After some playing around I can get it to

Hi, i use an BN4S0 with misdn an asterisk on Linux 2.6.9. The hfcmulti module is loaded with option: type=0x04 protocol=0x2,0x2,0x22,0x2 layermask=0xf,0xf,0xf,0xf and the fourth port is connected to an ISDN PTMP (MSN) port. Call to #72 from S0 (BN port 4) are not accepted from asterisk but why ? Can anyone give me a hint ?? misdn debug messages follows: lib: NEW_CR Ind with l3id:80001

I am trying to use misdn insted of zaphfc to drive two billion isdn cards zaphfc is ok, but the problem with cdr and the fact tha you always have to wait the bristuffed version of asterisk took me to try another way. so I downloaded the misdn installation script from beronet for the last version ( I am using asterisk stable 1.2, so now is 1.2.5) wget

I hadn't used FWD for quite a while. A customer sent me an email last week, "Is FWD broken when one tries to use it with IAX?" I have been playing around, and indeed seems to be the case. Is there anyone out there successfully using the two of them together? Thanks. B. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be

Hi, I''m asking my question here, because I could not find any answer to my problem, but I''m affraid shorewall is not the one to blame. First of all I''m using shorewall version 2.0.15 on two linux box. I set up an ipsec tunnel beetween those 2 boxes to be ables to connect 2 not routable subnetworks. Here is my network topology: 10.66.17.0/24 - 10.66.17.1 = eth0

Hi This is my 1st time here so please be gentle. I have encountered one problem since upgrading from 2.0.19 to 2.2.9 which has me beat. The system provides sasl auth services via inet to a postfix 2.11 system. Since the upgrade postfix complains of no sasl methods available. The same dovecot configuration is used on both versions. Now I get these results looking at the inet connection Version

hi i've configured a Beronet BN8S0 Card with misdn beronet utility. the card is configured with all lines in TE and P2P mode, and it is connected with the special cable with an ISDN connection. i've turned on debugging to level 4, this is the output from the asterisk cli when i receive a call: P[ 5] MGMT: Short status dinfo 1000001 P[ 5] MGMT: SSTATUS: L1_ACTIVATED P[ 5] handle_frm: