From owner-freebsd-isdn@FreeBSD.ORG Tue Aug 12 12:44:04 2014 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CCA49EC5 for ; Tue, 12 Aug 2014 12:44:04 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 91ABA291B for ; Tue, 12 Aug 2014 12:44:04 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id B895F1FE027 for ; Tue, 12 Aug 2014 14:44:02 +0200 (CEST) Message-ID: <53EA0C2C.5020007@selasky.org> Date: Tue, 12 Aug 2014 14:44:28 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "freebsd-isdn@freebsd.org" Subject: New version of ISDN4BSD in the works Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2014 12:44:04 -0000 Hi, My ISDN4BSD is making some steps into the TCP/IP domain. In the next version of ISDN4BSD, chan_capi will be extended to talk to remote CAPI devices. There are currently two supported protocols, BINTEC and a new ISDN4BSD only one. Example: env CAPI_CLIENT_HOST=10.70.4.21 asterisk At "10.70.4.21" an instance of a new utility called "capiserver" is running. This allows more simple devices to interface with the ISDN or hardware and then a more powerful computer can run the Asterisk in a jail, for example. Also ISDN4BSD will get support for emulating a Yealink USB phone device. To use this feature you will need a supported platform which has got a USB device port. This feature is currently used for interfacing towards telephony applications in non-FreeBSD systems. Or can be used in general, that when your USB audio is playing something, you will get an incoming call ... --HPS