Steve Haehnichen
2003-Sep-15 14:10 UTC
[Asterisk-Users] Anyone using National ISDN (NI-1) BRI under Linux?
I have a North American BRI configured as National ISDN (NI-1) on an SBC (Nortel?) switch. SBC calls this "FastTrak ISDN", and it's surprisingly inexpensive -- less than two POTS lines. I've been trying to find an inexpensive PCI interface solution to connect this to Asterisk as voice lines. I prefer ISDN BRI over POTS lines because of the improved signalling, fast dialing, clean audio, and so on. I've tried three different Passive ISDN boards supported by the HiSax drivers, with various degrees of failure. None have been able to complete a call. (Linux kernel 2.4.22, with AVM Fritz, DynaFax, and HFC cards) According to the HiSax documentation, NI-1 is a supported protocol.
Klaus-Peter Junghanns
2003-Sep-15 14:24 UTC
[Asterisk-Users] Anyone using National ISDN (NI-1) BRI under Linux?
Hi Steve, the Eicon Diva Server BRI cards support NI-1 with capi. Some people in .us are using them. Unfortunately AVM only put EuroISDN into their binary kernel module. :( Are you sure that incoming callerid is included in your "FastTrak ISDN"? i could imagine that SBC will rip you off extra for it! ;) regards kapejod -- Klaus-Peter Junghanns CEO,CTO Junghanns.NET GmbH Breite Strasse 13 - 12167 Berlin - Germany fon: +49 30 79705392 fax: +49 30 79705391 iaxtel: 1-700-157-8753 email: kpj@junghanns.net http://www.junghanns.net/asterisk Am Mon, 2003-09-15 um 23.10 schrieb Steve Haehnichen:> I have a North American BRI configured as National ISDN (NI-1) on an > SBC (Nortel?) switch. SBC calls this "FastTrak ISDN", and it's > surprisingly inexpensive -- less than two POTS lines. > > I've been trying to find an inexpensive PCI interface solution to > connect this to Asterisk as voice lines. I prefer ISDN BRI over POTS > lines because of the improved signalling, fast dialing, clean audio, > and so on. > > I've tried three different Passive ISDN boards supported by the HiSax > drivers, with various degrees of failure. None have been able to > complete a call. (Linux kernel 2.4.22, with AVM Fritz, DynaFax, and > HFC cards) > > According to the HiSax documentation, NI-1 is a supported protocol. > > From what I can find on CAPI, it supports only EuroISDN: > http://www.junghanns.net/asterisk/page15.html > Is this the case for all Linux CAPI drivers? Bummer. > > Has anyone successfully used Asterisk with a HiSax passive ISDN card > on a National-1 (or NI-2) dialing plan? It would really mean a whole > lot just to hear that someone is doing it with success. :) > > > How does one specify a SPID in Asterisk? I've done an archive search > and came up blank for "spid". BRI (2B+D) provisioning on SBC is done > with two Directory Numbers and two SPIDs, like this: > > DN1: 794-7601 > DN2: 794-7602 > > SPID1: 858-794-7601-0101 > SPID2: 858-794-7602-0101 > > (SBC said the -0101 is used on all NI-1 SPIDs) > > I'm not sure how to inform Asterisk/HiSax of the SPID part, and I get > a "SPID not supplied in EAZMSN" from the ISDN driver. > > I've tried various permutations of AT&E7947601:85879476010101 manually > into the /dev/ttyI0 interface, with no luck. > > Last, according to the kernel messages, there never seems to be an OAD > (Caller-ID) on incoming calls. I've used an ISDN protocol analyzer to > show that the incoming setup does contain the calling number. Again, > I'm just curious to compare notes with someone else doing this. > > Thanks! > > -Steve > > My modem.conf: > > [interfaces] > context=isdn-in > driver=i4l > language=en > type=autodetect > stripmsd=0 > dialtype=tone > mode=immediate > > group=1 > msn=7947601 > incomingmsn=* > context=isdn-in > device => /dev/ttyI0 > device => /dev/ttyI1 > > ------- > > My Kernel log: > > ISDN subsystem Rev: 1.1.4.1/1.1.4.1/1.1.4.1/none/1.1.4.1/1.1.4.1 loaded > HiSax: Linux Driver for passive ISDN cards > HiSax: Version 3.5 (module) > HiSax: Layer1 Revision 1.1.4.1 > HiSax: Layer2 Revision 1.1.4.1 > HiSax: TeiMgr Revision 1.1.4.1 > HiSax: Layer3 Revision 1.1.4.1 > HiSax: LinkLayer Revision 1.1.4.1 > HiSax: Total 1 card defined > HiSax: Card 1 Protocol NI1 Id=HFC (0) > HiSax: HFC-PCI driver Rev. 1.1.4.1 > HiSax: HFC-PCI card manufacturer: CCD/Billion/Asuscom card name: 2BD0 > HFC-PCI: defined at mem 0xe095dc00 fifo 0xd9e88000(0x19e88000) IRQ 5 HZ 100 > HFC_PCI: resetting card > HFC 2BDS0 PCI: IRQ 5 count 0 > HFC 2BDS0 PCI: IRQ 5 count 34 > HiSax: National ISDN-1 Rev. 1.1.4.1 > HiSax: National ISDN-1 Rev. 1.1.4.1 > HiSax: 2 channels added > HiSax: MAX_WAITING_CALLS added > ... > isdn_net: call from 0 -> 0 7947601 ignored > isdn_tty: Incoming call without OAD, assuming '0' > isdn_tty: call from 0, -> RING on ttyI1 > SPID not supplied in EAZMSN > isdn: HFC,ch0 cause: 001B > isdn: HFC,ch1 cause: 6F15 > isdn_net: Incoming call without OAD, assuming '0' > isdn_net: call from 0 -> 0 7947601 ignored > isdn_tty: Incoming call without OAD, assuming '0' > isdn_tty: call from 0, -> RING on ttyI0 > isdn_net: Incoming call without OAD, assuming '0' > isdn_net: call from 0 -> 0 7947601 ignored > isdn_tty: Incoming call without OAD, assuming '0' > isdn_tty: call from 0, -> RING on ttyI1 > isdn: HFC,ch0 cause: 001B > isdn_net: Incoming call without OAD, assuming '0' > isdn_net: call from 0 -> 0 7947601 ignored > isdn_tty: Incoming call without OAD, assuming '0' > isdn_tty: call from 0, -> RING on ttyI0 > SPID not supplied in EAZMSN > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users