From owner-freebsd-isdn@FreeBSD.ORG Tue Jun 10 19:08:26 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 023A837B401 for ; Tue, 10 Jun 2003 19:08:26 -0700 (PDT) Received: from hallie.shoalhaven.net.au (hallie.shoalhaven.net.au [202.139.20.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBF0F43F75 for ; Tue, 10 Jun 2003 19:08:24 -0700 (PDT) (envelope-from jaster@shoalhaven.net.au) Received: from lan5.internal.lan (om11.shoalhaven.net.au [202.139.20.11]) h5B28Od0007198 for ; Wed, 11 Jun 2003 12:08:24 +1000 (EST) From: Joshua Silver To: freebsd-isdn@freebsd.org Date: Wed, 11 Jun 2003 12:08:21 +1000 User-Agent: KMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200306111208.21922.jaster@shoalhaven.net.au> Subject: 56k DoV X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jaster@shoalhaven.net.au List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 02:08:26 -0000 Hi All, I have just setup an ISDN connection using a NetJet-S PCI card. Card detects fine, and I can make 64k Data calls no prob, but when I try to do a DoV call, it don't want to play ball .... dooh .... :( A little research, and i've found out my ISP uses Ascend MAX 6000's, which will only accept 56k DoV, not 64k DoV. I've put the NetJet card into a Windoze machine and had the expected results, it does 64k Data calls, it fails with 64k DoV, but works fine with 56k DoV, so I know it can work. The prob i've got is I can't find the relevant bearer cap codes anywhere for 56k DoV ... I can find the other two everywhere on the net, 0x8890 for 64k Data, and 0x9090A3 for 64k DoV, but can't find any info what the 56k DoV setting should be. I was hoping some one out there has the answer to my problem. Thanks in advance, Josh. From owner-freebsd-isdn@FreeBSD.ORG Tue Jun 10 21:25:32 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AF9437B401 for ; Tue, 10 Jun 2003 21:25:32 -0700 (PDT) Received: from nexus.tmp.com.br (nexus.tmp.com.br [200.255.204.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9820443F75 for ; Tue, 10 Jun 2003 21:25:30 -0700 (PDT) (envelope-from prallon@nexus.tmp.com.br) Received: (from prallon@localhost) by nexus.tmp.com.br (8.8.8/8.8.8) id BAA02703 for freebsd-isdn@freebsd.org; Wed, 11 Jun 2003 01:25:28 -0300 Resent-Message-Id: <200306110425.BAA02703@nexus.tmp.com.br> Date: Wed, 11 Jun 2003 01:17:45 -0300 From: Sergio de Souza Prallon To: Joshua Silver Message-ID: <20030611011745.A2302@tmp.com.br> References: <200306111208.21922.jaster@shoalhaven.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200306111208.21922.jaster@shoalhaven.net.au>; from jaster@shoalhaven.net.au on Wed, Jun 11, 2003 at 12:08:21PM +1000 X-URL: http://www.tmp.com.br Resent-From: prallon@tmp.com.br Resent-Date: Wed, 11 Jun 2003 01:25:28 -0300 Resent-To: freebsd-isdn@freebsd.org Subject: Re: 56k DoV X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 04:25:32 -0000 Hi, I wrote the driver for this card, but I never had any experience with DoV (it's not an issue in my country). AFAIK, involves "cheating" the bearer codes (which can be done - there is at least one patch from NetJet Inc for it) AND (in the 56K case) ignore the 7th bit of every byte sent or received does not exists while enconding or decoding the HDLC frames. Unfortunately, this is not handled by the HDLC encoder/decoder package I use. It may be possible to hack it, but I don't know for sure, the code is heavily optimized. I'd sugest you to contact Hans Petter Selasky, the original author of the encoder. Hope this helps. []'s -- Prallon On Wed, Jun 11, 2003 at 12:08:21PM +1000, Joshua Silver wrote: > Hi All, > > I have just setup an ISDN connection using a NetJet-S PCI card. Card detects > fine, and I can make 64k Data calls no prob, but when I try to do a DoV call, > it don't want to play ball .... dooh .... :( > > A little research, and i've found out my ISP uses Ascend MAX 6000's, which > will only accept 56k DoV, not 64k DoV. I've put the NetJet card into a > Windoze machine and had the expected results, it does 64k Data calls, it > fails with 64k DoV, but works fine with 56k DoV, so I know it can work. > > The prob i've got is I can't find the relevant bearer cap codes anywhere for > 56k DoV ... I can find the other two everywhere on the net, 0x8890 for 64k > Data, and 0x9090A3 for 64k DoV, but can't find any info what the 56k DoV > setting should be. > > I was hoping some one out there has the answer to my problem. > > Thanks in advance, > > Josh. > _______________________________________________ > freebsd-isdn@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isdn > To unsubscribe, send any mail to "freebsd-isdn-unsubscribe@freebsd.org" From owner-freebsd-isdn@FreeBSD.ORG Wed Jun 11 06:05:06 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 144E137B401 for ; Wed, 11 Jun 2003 06:05:06 -0700 (PDT) Received: from fep04-svc.swip.net (fep04.swip.net [130.244.199.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA4B343F85 for ; Wed, 11 Jun 2003 06:05:04 -0700 (PDT) (envelope-from hselasky@c2i.net) Received: from curly.tele2.no ([193.216.48.223]) by fep04-svc.swip.net with ESMTP id <20030611130502.DLVW16434.fep04-svc.swip.net@curly.tele2.no>; Wed, 11 Jun 2003 15:05:02 +0200 Received: (from root@localhost) by curly.tele2.no (8.12.5/8.12.3) id h5BDAsqJ020425; Wed, 11 Jun 2003 15:10:54 +0200 (CEST) (envelope-from hselasky@c2i.net) Date: Wed, 11 Jun 2003 15:10:53 +0200 From: Hans Petter Selasky & To: Sergio de Souza Prallon , Joshua Silver , freebsd-isdn@freebsd.org Message-ID: <20030611151053.B20101@curly.tele2.no> References: <200306111208.21922.jaster@shoalhaven.net.au> <20030611011745.A2302@tmp.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030611011745.A2302@tmp.com.br>; from prallon@tmp.com.br on Wed, Jun 11, 2003 at 01:17:45AM -0300 Subject: Re: 56k DoV X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 13:05:06 -0000 Hi, I wrote the HDLC encoder/decoder. Q.921's definition of HDLC is a serial (1-bit) protocol, that transfers 8-bit units of data. I'd assume this is the same for all transferrates. If I'm right, all you have to do, is to move the bits around, so that the serial data stream is the same. Bits are transmitted in the order bit[0] to bit[7] inclusively (64k). When using 56k there are two logical choices of unused bits: Either bit[0] or bit[7] can be set to either zero or one. According to the HFC-S manual, setting bit[0] (LSB) to one is default when using 56k mode. To decide for sure what format your ISP is using, I'd need a data-stream sample. What version of FreeBSD are you using? On Wed, Jun 11, 2003 at 01:17:45AM -0300, Sergio de Souza Prallon wrote: > Hi, > > I wrote the driver for this card, but I never had any experience with DoV > (it's not an issue in my country). AFAIK, involves "cheating" the bearer > codes (which can be done - there is at least one patch from NetJet Inc > for it) AND (in the 56K case) ignore the 7th bit of every byte sent or > received does not exists while encoding or decoding the HDLC frames. > Unfortunately, this is not handled by the HDLC encoder/decoder package I > use. It may be possible to hack it, but I don't know for sure, the code > is heavily optimized. I'd suggest you to contact Hans Petter Selasky, the > original author of the encoder. > > Hope this helps. > > []'s > > -- > Prallon > > > > On Wed, Jun 11, 2003 at 12:08:21PM +1000, Joshua Silver wrote: > > Hi All, > > > > I have just setup an ISDN connection using a NetJet-S PCI card. Card detects > > fine, and I can make 64k Data calls no prob, but when I try to do a DoV call, > > it don't want to play ball .... dooh .... :( > > > > A little research, and I've found out my ISP uses Ascend MAX 6000's, which > > will only accept 56k DoV, not 64k DoV. I've put the NetJet card into a > > Windoze machine and had the expected results, it does 64k Data calls, it > > fails with 64k DoV, but works fine with 56k DoV, so I know it can work. > > > > The prob I've got is I can't find the relevant bearer cap codes anywhere for > > 56k DoV ... I can find the other two everywhere on the net, 0x8890 for 64k > > Data, and 0x9090A3 for 64k DoV, but can't find any info what the 56k DoV > > setting should be. > > > > I was hoping some one out there has the answer to my problem. > > > > Thanks in advance, > > > > Josh. Yours --HPS From owner-freebsd-isdn@FreeBSD.ORG Thu Jun 12 22:29:44 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D91937B401 for ; Thu, 12 Jun 2003 22:29:44 -0700 (PDT) Received: from hallie.shoalhaven.net.au (hallie.shoalhaven.net.au [202.139.20.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B1C543FCB for ; Thu, 12 Jun 2003 22:29:43 -0700 (PDT) (envelope-from jaster@shoalhaven.net.au) Received: from lan5.internal.lan (om11.shoalhaven.net.au [202.139.20.11]) h5D5Tewo065715 for ; Fri, 13 Jun 2003 15:29:41 +1000 (EST) From: Joshua Silver To: freebsd-isdn@freebsd.org Date: Fri, 13 Jun 2003 15:29:38 +1000 User-Agent: KMail/1.5.2 References: <200306111208.21922.jaster@shoalhaven.net.au> <20030611011745.A2302@tmp.com.br> <20030611151053.B20101@curly.tele2.no> In-Reply-To: <20030611151053.B20101@curly.tele2.no> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200306131529.38864.jaster@shoalhaven.net.au> Subject: Re: 56k DoV X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jaster@shoalhaven.net.au List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2003 05:29:44 -0000 Thanks Guys, I've done a little more digging, and found your right, it's a little more complicated than I thought ... dang :( ... I'm running 4.8-STABLE, and when you say you need a data stream, is that something like the output from isdn_trace ? ... sorry, i'm still rather new to ISDN ... ;) Josh. On Wed, 11 Jun 2003 23:10, Hans Petter Selasky & wrote: > *This message was transferred with a trial version of CommuniGate(tm) Pro* > Hi, > > I wrote the HDLC encoder/decoder. Q.921's definition of HDLC is a serial > (1-bit) protocol, that transfers 8-bit units of data. I'd assume this is > the same for all transferrates. If I'm right, all you have to do, is to > move the bits around, so that the serial data stream is the same. Bits are > transmitted in the order bit[0] to bit[7] inclusively (64k). When using 56k > there are two logical choices of unused bits: Either bit[0] or bit[7] can > be set to either zero or one. According to the HFC-S manual, setting bit[0] > (LSB) to one is default when using 56k mode. > > To decide for sure what format your ISP is using, I'd need a data-stream > sample. What version of FreeBSD are you using? > > On Wed, Jun 11, 2003 at 01:17:45AM -0300, Sergio de Souza Prallon wrote: > > Hi, > > > > I wrote the driver for this card, but I never had any experience with DoV > > (it's not an issue in my country). AFAIK, involves "cheating" the bearer > > codes (which can be done - there is at least one patch from NetJet Inc > > for it) AND (in the 56K case) ignore the 7th bit of every byte sent or > > received does not exists while encoding or decoding the HDLC frames. > > Unfortunately, this is not handled by the HDLC encoder/decoder package I > > use. It may be possible to hack it, but I don't know for sure, the code > > is heavily optimized. I'd suggest you to contact Hans Petter Selasky, the > > original author of the encoder. > > > > Hope this helps. > > > > []'s > > > > -- > > Prallon > > From owner-freebsd-isdn@FreeBSD.ORG Fri Jun 13 10:43:44 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A34F037B401 for ; Fri, 13 Jun 2003 10:43:44 -0700 (PDT) Received: from fep04-svc.swip.net (fep04.swip.net [130.244.199.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13B1C43F75 for ; Fri, 13 Jun 2003 10:43:43 -0700 (PDT) (envelope-from hselasky@c2i.net) Received: from curly.tele2.no ([193.217.231.152]) by fep04-svc.swip.net with ESMTP id <20030613174340.IFSW9872.fep04-svc.swip.net@curly.tele2.no>; Fri, 13 Jun 2003 19:43:40 +0200 Received: (from root@localhost) by curly.tele2.no (8.12.5/8.12.3) id h5DHnfGR001426; Fri, 13 Jun 2003 19:49:41 +0200 (CEST) (envelope-from hselasky@c2i.net) Date: Fri, 13 Jun 2003 19:49:20 +0200 From: Hans Petter Selasky & To: Joshua Silver , freebsd-isdn@freebsd.org Message-ID: <20030613194920.A1294@curly.tele2.no> References: <200306111208.21922.jaster@shoalhaven.net.au> <20030611011745.A2302@tmp.com.br> <20030611151053.B20101@curly.tele2.no> <200306131529.38864.jaster@shoalhaven.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200306131529.38864.jaster@shoalhaven.net.au>; from jaster@shoalhaven.net.au on Fri, Jun 13, 2003 at 03:29:38PM +1000 Subject: Re: 56k DoV X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2003 17:43:45 -0000 Hi. isdntrace is currently not capable of tracing the B-channel unless the device is connected. I've scratched together a small program that will fetch a data sample. I assume that you only have one ISDN card in your computer. The program will use BPROT_NONE: cd ~ fetch http://home.c2i.net/hselasky/isdn4bsd/privat/temporary/isdntest.tar.gz tar -zxvf isdntest.tar.gz cd isdntest make clean all ./isdntest After you got the program working, you need to do some editing: cd /sys/i4b/layer3/ "i4b_q931.h": Add the following line after the line saying IT_RATE_64K #define IT_RATE_56K 0x8f /* BC: information xfer rate (not tested) */ then make a backup (same directory) cp i4b_l2if.c i4b_l2if.c.bak "i4b_l2if.c": Search forward to the function "i4b_l3_tx_setup". Then under "case BRPROT_NONE:" change IT_RATE_64K to IT_RATE_56K, recompile the kernel, reboot and run my program. If the program connects, you might want to redefine IT_RATE_56K to IT_RATE_64K, so that it does not cause trouble with other programs. If the program doesn't connect, you need two computers: One computer to dial 56k DoV and another computer to trace the D-channel. See /usr/src/usr.sbin/i4b/isdntrace/ and /usr/src/usr.sbin/i4b/isdntrace/cable.txt for more information. On Fri, Jun 13, 2003 at 03:29:38PM +1000, Joshua Silver wrote: > Thanks Guys, > > I've done a little more digging, and found your right, it's a little more > complicated than I thought ... dang :( ... > > I'm running 4.8-STABLE, and when you say you need a data stream, is that > something like the output from isdn_trace ? ... sorry, I'm still rather new > to ISDN ... ;) > > Josh. > > On Wed, 11 Jun 2003 23:10, Hans Petter Selasky & wrote: > > Hi, > > > > I wrote the HDLC encoder/decoder. Q.921's definition of HDLC is a serial > > (1-bit) protocol, that transfers 8-bit units of data. I'd assume this is > > the same for all transferrates. If I'm right, all you have to do, is to > > move the bits around, so that the serial data stream is the same. Bits are > > transmitted in the order bit[0] to bit[7] inclusively (64k). When using 56k > > there are two logical choices of unused bits: Either bit[0] or bit[7] can > > be set to either zero or one. According to the HFC-S manual, setting bit[0] > > (LSB) to one is default when using 56k mode. > > > > To decide for sure what format your ISP is using, I'd need a data-stream > > sample. What version of FreeBSD are you using? > > > > On Wed, Jun 11, 2003 at 01:17:45AM -0300, Sergio de Souza Prallon wrote: > > > Hi, > > > > > > I wrote the driver for this card, but I never had any experience with DoV > > > (it's not an issue in my country). AFAIK, involves "cheating" the bearer > > > codes (which can be done - there is at least one patch from NetJet Inc > > > for it) AND (in the 56K case) ignore the 7th bit of every byte sent or > > > received does not exists while encoding or decoding the HDLC frames. > > > Unfortunately, this is not handled by the HDLC encoder/decoder package I > > > use. It may be possible to hack it, but I don't know for sure, the code > > > is heavily optimized. I'd suggest you to contact Hans Petter Selasky, the > > > original author of the encoder. > > > > > > Hope this helps. > > > > > > []'s > > > > > > -- > > > Prallon > > > Yours --HPS