From owner-freebsd-isdn@FreeBSD.ORG Mon Dec 8 10:04:09 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 26EEA16A4CE for ; Mon, 8 Dec 2003 10:04:09 -0800 (PST) Received: from msg01.ip2.net (msg01.ip2.net [212.125.141.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1C2943F75 for ; Mon, 8 Dec 2003 10:04:07 -0800 (PST) (envelope-from jbaggen@ip2.nl) Received: from pc01 (bck01.ip2.net [213.84.28.9]) (authenticated bits=0) by msg01.ip2.net (8.12.10/8.12.10) with ESMTP id hB8I4Vx1011172 for ; Mon, 8 Dec 2003 19:04:31 +0100 (CET) (envelope-from jbaggen@ip2.nl) From: "Jan Baggen" To: Date: Mon, 8 Dec 2003 19:05:43 +0100 Message-ID: <000501c3bdb5$e8d2df90$0101a8c0@pc01> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: EICON DIVA 4-BRI 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: Mon, 08 Dec 2003 18:04:09 -0000 Is the EICON DIVA 4-BRI PCI card supported by FreeBSD? I'm trying to setup this card for hylafax. --- Jan Baggen - jbaggen@ip2.nl IP2 Internet BV / http://www.ip2.nl From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 11 15:17:53 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 819A416A4CE for ; Thu, 11 Dec 2003 15:17:53 -0800 (PST) Received: from mail4.ewetel.de (mail4-141.ewetel.de [212.6.122.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id B80C743D1F for ; Thu, 11 Dec 2003 15:17:51 -0800 (PST) (envelope-from twinterg@gmx.de) Received: from kalak.lemur.nord.de (dialin-80-228-49-104.ewe-ip-backbone.de [80.228.49.104]) by mail4.ewetel.de (8.12.1/8.12.9) with ESMTP id hBBNHZZD002863; Fri, 12 Dec 2003 00:17:36 +0100 (MET) Received: from gmx.de (lullog-w2k.lemur.nord.de [192.168.2.132]) by kalak.lemur.nord.de (8.12.3/8.12.3) with ESMTP id hBBNBPDL004931; Fri, 12 Dec 2003 00:11:25 +0100 (CET) (envelope-from twinterg@gmx.de) Message-ID: <3FD8F99D.5010808@gmx.de> Date: Fri, 12 Dec 2003 00:11:25 +0100 From: Thomas Wintergerst User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: Jan Baggen References: <000501c3bdb5$e8d2df90$0101a8c0@pc01> In-Reply-To: <000501c3bdb5$e8d2df90$0101a8c0@pc01> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-CheckCompat: OK cc: freebsd-isdn@freebsd.org Subject: Re: EICON DIVA 4-BRI 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: Thu, 11 Dec 2003 23:17:53 -0000 Hi Jan, Unfortunately this board is currently not supported (AFAIK). Maybe it will be supported sometime by c4b (CAPI for BSD) and then also by i4b. But this will not happen in the very near future. Although I would like to implement a driver for it, it will be a lot of work (not so "easy" like the active AVM boards). And I will have to make some discussions with Eicon for information about programming their boards. Jan Baggen wrote: > Is the EICON DIVA 4-BRI PCI card supported by FreeBSD? > > I'm trying to setup this card for hylafax. > > --- > Jan Baggen - jbaggen@ip2.nl > IP2 Internet BV / http://www.ip2.nl > > _______________________________________________ > 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" > -- Gruss, Thomas -- From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 11 15:22:17 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 3234716A4CE for ; Thu, 11 Dec 2003 15:22:17 -0800 (PST) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id EC3EC43D39 for ; Thu, 11 Dec 2003 15:22:14 -0800 (PST) (envelope-from un1du2el@gmx.net) Received: (qmail 8991 invoked by uid 0); 11 Dec 2003 23:22:13 -0000 Received: from 212.144.192.43 by www54.gmx.net with HTTP; Fri, 12 Dec 2003 00:22:13 +0100 (MET) Date: Fri, 12 Dec 2003 00:22:13 +0100 (MET) From: "Markus D." To: isdn@freebsd.org MIME-Version: 1.0 X-Priority: 3 (Normal) X-Authenticated: #931807 Message-ID: <13460.1071184933@www54.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: "Access information discarded" in 5.1-Release 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: Thu, 11 Dec 2003 23:22:17 -0000 Hello, since I use Freebsd 5.1-RELASE with my isdn gateway,I always get an "access information discarded" on the first dial attempt (with rbch/ppp as well as with ippp). The second dial attempt completes and tun/isp is established. Following is a isdntrace of a connection setup: ##### start ##### -- TE->NT - unit:0 - frame:000061 - time:12.12 00:06:28.407157 - length:91 ----- Dump:004 08 01 3d 05 a1 04 02 88 90 18 01 83 6c 08 81 38 ..=.........l..8 Dump:020 38 36 38 39 30 37 6d 16 80 bf d6 93 17 28 18 76 868907m......(.v Dump:036 1a 28 03 82 06 08 68 fb bf bf 92 80 05 08 70 08 .(....h.......p. Dump:052 81 30 31 39 32 30 37 31 71 1d 80 9b 16 28 02 fd .0192071q....(.. Dump:068 18 28 40 2a 1a 28 28 fb bf bf 54 56 19 28 a0 3e .(@*.((...TV.(.> Dump:084 38 38 36 38 39 30 37 8868907 Q931: pd=Q.931/I.451, cr=0x3d (from origination), message=SETUP: [sending complete] [bearer capability: cap=unrestricted digital information std=CCITT rate=64 kbit/s mode=circuit] [channel id: channel=any channel (preferred)] [calling party number: 8868907 (type=unknown, plan=ISDN)] [calling party subaddress: LEN=0x16, DATA=0x80 0xbf 0xd6 0x93 0x17 0x28 0x18 0x76 0x1a 0x28 0x03 0x82 0x06 0x08 0x68 0xfb 0xbf 0xbf 0x92 0x80 0x05 0x08 ] [called party number: 0192071 (type=unknown, plan=ISDN)] [called party subaddress: LEN=0x1d, DATA=0x80 0x9b 0x16 0x28 0x02 0xfd 0x18 0x28 0x40 0x2a 0x1a 0x28 0x28 0xfb 0xbf 0xbf 0x54 0x56 0x19 0x28 0xa0 0x3e 0x38 0x38 0x36 0x38 0x39 0x30 0x37 ] -- NT->TE - unit:0 - frame:000063 - time:12.12 00:06:28.597156 - length:15 ----- Dump:004 08 01 bd 7d 08 02 82 ab 14 01 01 ...}....... Q931: pd=Q.931/I.451, cr=0x3d (from destination), message=STATUS: [cause: 43: Access information discarded (Q.850) (location=public network serving local user, std=CCITT)] [call state: Std=CCITT, State=Call initiated] -- TE->NT - unit:0 - frame:000064 - time:12.12 00:06:28.597156 - length:12 ----- Dump:004 08 01 3d 45 08 02 80 e5 ..=E.... Q931: pd=Q.931/I.451, cr=0x3d (from origination), message=DISCONNECT: [cause: 101: Message not compatible with call state (Q.850) (location=user, std=CCITT)] -- NT->TE - unit:0 - frame:000066 - time:12.12 00:06:29.187165 - length:8 ------ Dump:004 08 01 bd 4d ...M Q931: pd=Q.931/I.451, cr=0x3d (from destination), message=RELEASE: -- TE->NT - unit:0 - frame:000067 - time:12.12 00:06:29.187165 - length:8 ------ Dump:004 08 01 3d 5a ..=Z-- TE->NT - unit:0 - frame:000070 - time:12.12 00:06:34.237241 - length:56 ----- Dump:004 08 01 09 05 a1 04 02 88 90 18 01 83 6c 08 81 38 ............l..8 Dump:020 38 36 38 39 30 37 6d 0b 80 bf 3d 68 05 08 40 43 868907m...=h..@C Dump:036 07 08 02 70 08 81 30 31 39 32 30 37 31 71 05 80 ...p..0192071q.. Dump:052 d2 05 08 40 ...@ Q931: pd=Q.931/I.451, cr=0x09 (from origination), message=SETUP: [sending complete] [bearer capability: cap=unrestricted digital information std=CCITT rate=64 kbit/s mode=circuit] [channel id: channel=any channel (preferred)] [calling party number: 8868907 (type=unknown, plan=ISDN)] [calling party subaddress: LEN=0x0b, DATA=0x80 0xbf 0x3d 0x68 0x05 0x08 0x40 0x43 0x07 0x08 0x02 ] [called party number: 0192071 (type=unknown, plan=ISDN)] [called party subaddress: LEN=0x05, DATA=0x80 0xd2 0x05 0x08 0x40 ] -- NT->TE - unit:0 - frame:000072 - time:12.12 00:06:34.517245 - length:11 ----- Dump:004 08 01 89 02 18 01 89 ....... Q931: pd=Q.931/I.451, cr=0x09 (from destination), message=CALL PROCEEDING: [channel id: channel=B-1 (exclusive)] -- NT->TE - unit:0 - frame:000074 - time:12.12 00:06:35.057253 - length:15 ----- Dump:004 08 01 89 07 29 05 03 0c 0c 00 06 ....)...... Q931: pd=Q.931/I.451, cr=0x09 (from destination), message=CONNECT: [date/time: 12.12.03 00:06] -- TE->NT - unit:0 - frame:000075 - time:12.12 00:06:35.057253 - length:8 ------ Dump:004 08 01 09 0f .... Q931: pd=Q.931/I.451, cr=0x09 (from origination), message=CONNECT ACKNOWLEDGE: Q931: pd=Q.931/I.451, cr=0x3d (from origination), message=RELEASE COMPLETE: ##### end ##### As I can see, the calling and called party subaddress contains some extra infomation in the first setup message. I'm not familiar with isdn. What is this? Can I configure this? BTW: The ISP is German Arcor. Thanks Markus