From owner-freebsd-isdn@FreeBSD.ORG Tue May 10 13:18:49 2005 Return-Path: Delivered-To: freebsd-isdn@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2816516A4D0; Tue, 10 May 2005 13:18:49 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1DE143D68; Tue, 10 May 2005 13:18:48 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j4ADImpT051365; Tue, 10 May 2005 13:18:48 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4ADImLY051361; Tue, 10 May 2005 13:18:48 GMT (envelope-from arved) Date: Tue, 10 May 2005 13:18:48 GMT From: Tilman Linneweh Message-Id: <200505101318.j4ADImLY051361@freefall.freebsd.org> To: arved@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-isdn@FreeBSD.org Subject: Re: kern/79117: iavc(4) for AVM B1 PCI does not attach 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: Tue, 10 May 2005 13:18:49 -0000 Synopsis: iavc(4) for AVM B1 PCI does not attach Responsible-Changed-From-To: freebsd-bugs->freebsd-isdn Responsible-Changed-By: arved Responsible-Changed-When: Tue May 10 13:18:31 GMT 2005 Responsible-Changed-Why: over to ISDN mailinglist http://www.freebsd.org/cgi/query-pr.cgi?pr=79117 From owner-freebsd-isdn@FreeBSD.ORG Tue May 10 13:23:17 2005 Return-Path: Delivered-To: freebsd-isdn@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F54F16A4CE; Tue, 10 May 2005 13:23:17 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6812943D68; Tue, 10 May 2005 13:23:17 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j4ADNHdR051726; Tue, 10 May 2005 13:23:17 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4ADNHxr051722; Tue, 10 May 2005 13:23:17 GMT (envelope-from arved) Date: Tue, 10 May 2005 13:23:17 GMT From: Tilman Linneweh Message-Id: <200505101323.j4ADNHxr051722@freefall.freebsd.org> To: arved@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-isdn@FreeBSD.org Subject: Re: kern/76611: i4b itjc bad enums for PIB cycle time 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: Tue, 10 May 2005 13:23:17 -0000 Synopsis: i4b itjc bad enums for PIB cycle time Responsible-Changed-From-To: freebsd-bugs->freebsd-isdn Responsible-Changed-By: arved Responsible-Changed-When: Tue May 10 13:23:00 GMT 2005 Responsible-Changed-Why: Over to ISDN Mailinglist http://www.freebsd.org/cgi/query-pr.cgi?pr=76611 From owner-freebsd-isdn@FreeBSD.ORG Wed May 11 13:32:02 2005 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 4B58216A4CE for ; Wed, 11 May 2005 13:32:02 +0000 (GMT) Received: from gvr.gvr.org (gvr-gw.gvr.org [80.126.103.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id C97D543D75 for ; Wed, 11 May 2005 13:32:01 +0000 (GMT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 2F0CFC0F0; Wed, 11 May 2005 15:32:01 +0200 (CEST) Date: Wed, 11 May 2005 15:32:01 +0200 From: Guido van Rooij To: freebsd-isdn@freebsd.org Message-ID: <20050511133201.GA65931@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: longshine isdn lcs-8051 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 May 2005 13:32:02 -0000 Is this (Cologne HFC-S PCI A Chipset based) card supported? Apparently, this chipset is able to be used in NT (vs TE) mode making it suitable for homegrown PBX use. Is this at all supported in FreeBSD? (the file layer1/ihfc/i4b_ihfc_drv.c seems to point at that direction: the comment just above ihfc_control() says: * Flag: * 1: reset and unlock chip (at boot only) * 2: prepare for shutdown (at shutdown only) * 3: reset and resume * 4: select TE-mode (boot default) * 5: select NT-mode (only HFC-S/SP/PCI) ) -Guido From owner-freebsd-isdn@FreeBSD.ORG Wed May 11 14:11:56 2005 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 46C6B16A4CE for ; Wed, 11 May 2005 14:11:56 +0000 (GMT) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 765A543D5C for ; Wed, 11 May 2005 14:11:55 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-200-170.daxnet.no ([193.217.200.170] verified) by mailfe06.swip.net (CommuniGate Pro SMTP 4.3c5) with ESMTP id 352515256; Wed, 11 May 2005 16:11:53 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Wed, 11 May 2005 16:12:32 +0200 User-Agent: KMail/1.7 References: <20050511133201.GA65931@gvr.gvr.org> In-Reply-To: <20050511133201.GA65931@gvr.gvr.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505111612.32902.hselasky@c2i.net> cc: Guido van Rooij Subject: Re: longshine isdn lcs-8051 X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2005 14:11:56 -0000 On Wednesday 11 May 2005 15:32, Guido van Rooij wrote: > Is this (Cologne HFC-S PCI A Chipset based) card supported? > Apparently, this chipset is able to be used in NT (vs TE) mode > making it suitable for homegrown PBX use. Is this at all supported > in FreeBSD? (the file layer1/ihfc/i4b_ihfc_drv.c seems to point > at that direction: the comment just above ihfc_control() says: There is a combo ISDN/USB-driver for FreeBSD-5/6 available from: http://home.c2i.net/hselasky/isdn4bsd/privat/temporary/ which supports HFC-S PCI A. NT-mode is supported, but I have only implemented the NT version of the DSS1 protocol. The driver info document describes briefly how to use this protocol, and the new ihfc manpage describes how to build a NT<->TE crossover cable. If you don't want to run "isdnd", you can set NT-mode, cable-activation and B-/D-channel protocol from "isdndebug", and access the B-/D-channels directly through /dev/ihfcX.X. Yours --HPS From owner-freebsd-isdn@FreeBSD.ORG Fri May 13 11:34:50 2005 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 4D33716A4CE for ; Fri, 13 May 2005 11:34:50 +0000 (GMT) Received: from mail.turbocat.net (mail.turbocat.net [213.133.116.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6B8F43D41 for ; Fri, 13 May 2005 11:34:49 +0000 (GMT) (envelope-from dave@turbocat.de) Received: by mail.turbocat.net (Postfix, from userid 1002) id 78804422ECAC; Fri, 13 May 2005 13:34:46 +0200 (CEST) Received: from alice.turbocat.de (p54BCCE27.dip.t-dialin.net [84.188.206.39]) by mail.turbocat.net (Postfix) with ESMTP id 4D1B8422EC99 for ; Fri, 13 May 2005 13:34:45 +0200 (CEST) Received: from testhost (alice [10.1.0.1]) by alice.turbocat.de (Postfix) with ESMTP id EF9AF1EAE27C for ; Fri, 13 May 2005 13:34:45 +0200 (CEST) X-Mailer: TCMail 2.0 http://www.turbocat.de (NetBSD) From: David Wetzel Date: Fri, 13 May 2005 13:34:45 +0200 To: freebsd-isdn@freebsd.org X-Originating-IP: [62.245.84.166] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-TCMailFlags: 001 Message-Id: <20050513113445.EF9AF1EAE27C@alice.turbocat.de> Subject: answering calls 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 May 2005 11:34:50 -0000 hi folks, I try to create a lib to wrap the i4b telephony stuff in a way that makes it easy to use from external programs. I do this as a first step to add i4b support to Asterisk. I do not intent to run the isdnd. Imagine there are N different ISDN cards in the system. Some may be Fritz with 2 channels some may have a PRI with 30 channels. If I understand the documentation right, all signaling and accept/reject control is made via /dev/isdn and the real voice data will flow via /dev/isdntel* On an incoming call, I get the stuct msg_connect_ind_t which contains controller and channel number. The driver's int number I seem to get via lookup_l4_driver() from rc_config.c. But how to get the driver_unit? How do I know which /dev/isdntel* to use? Can i4b find the right driver/unit based on the cdid? Thanks! dave --- _ _ _(_)(_)_ David Wetzel, Turbocat's Development, (_) __ (_) Buchhorster Strasse 23, D-16567 Muehlenbeck/Berlin, FRG, _/ \_ Fax +49 33056 82835 Phone +49 33056 82834 (______) http://www.turbocat.de/ From owner-freebsd-isdn@FreeBSD.ORG Fri May 13 14:05:47 2005 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 206C816A4CE for ; Fri, 13 May 2005 14:05:46 +0000 (GMT) Received: from swip.net (mailfe10.swipnet.se [212.247.155.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5CE743D54 for ; Fri, 13 May 2005 14:05:44 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-202-122.daxnet.no ([193.217.202.122] verified) by mailfe10.swip.net (CommuniGate Pro SMTP 4.3c5) with ESMTP id 157068607; Fri, 13 May 2005 16:05:43 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Fri, 13 May 2005 16:06:27 +0200 User-Agent: KMail/1.7 References: <20050513113445.EF9AF1EAE27C@alice.turbocat.de> In-Reply-To: <20050513113445.EF9AF1EAE27C@alice.turbocat.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505131606.28752.hselasky@c2i.net> Subject: Re: answering calls X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2005 14:05:47 -0000 On Friday 13 May 2005 13:34, David Wetzel wrote: > hi folks, > > I try to create a lib to wrap the i4b telephony stuff in a way that makes > it easy to use from external programs. I do this as a first step to add i4b > support to Asterisk. I do not intent to run the isdnd. > > Imagine there are N different ISDN cards in the system. Some may be Fritz > with 2 channels some may have a PRI with 30 channels. > > If I understand the documentation right, all signaling and accept/reject > control is made via /dev/isdn and the real voice data will flow via > /dev/isdntel* > > On an incoming call, I get the stuct msg_connect_ind_t which contains > controller and channel number. > > The driver's int number I seem to get via lookup_l4_driver() from > rc_config.c. > > But how to get the driver_unit? > How do I know which /dev/isdntel* to use? > The "/dev/isdntel*" are shared among all [ISDN-] controllers. It is isdnd's job to manage which controller gets connected to which "driver" and "driver_unit". When an incoming call is present this is done by replying with one of two messages: Here is a cp from my driver: /*---------------------------------------------------------------------------* * connect response * this is the answer to an incoming connect indication *---------------------------------------------------------------------------*/ typedef struct { cdid_t cdid; /* call descriptor id */ int response; /* what to do with incoming call */ #define SETUP_RESP_DNTCRE 0 /* don't care, call is not for me */ #define SETUP_RESP_REJECT 1 /* reject call */ #define SETUP_RESP_ACCEPT 2 /* accept call */ cause_t cause; /* cause for case SETUP_RESP_REJECT */ /* the following are only used for SETUP_RESP_ACCEPT !! */ int txdelay; /* tx delay after connect */ int bprot; /* B chan protocol */ int driver; /* driver to route b channel data to */ int driver_unit; /* unit number for above driver */ int max_idle_time; /* max time without activity on b ch */ } msg_connect_resp_t; I've also got the option to just alert: /*---------------------------------------------------------------------------* * send alert request *---------------------------------------------------------------------------*/ typedef struct { cdid_t cdid; /* call descriptor id */ } msg_alert_req_t; But recently there were some discussions about making the drivers like "/dev/i4btel*" dynamic, so maybe that will mean that there will be a static association between "/dev/i4btel*" and a certain controller and B-channel. --HPS