From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 9 09:16:12 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C17B21065671 for ; Sun, 9 Mar 2008 09:16:12 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.freebsd.org (Postfix) with ESMTP id 541A18FC17 for ; Sun, 9 Mar 2008 09:16:12 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [62.113.132.89] (account mc467741@c2i.net [62.113.132.89] verified) by mailfe06.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 841500610; Sun, 09 Mar 2008 10:16:10 +0100 From: Hans Petter Selasky To: "Max Laier" Date: Sun, 9 Mar 2008 10:17:14 +0100 User-Agent: KMail/1.9.7 References: <200803081133.02575.hselasky@c2i.net> <49726.192.168.4.151.1204973365.squirrel@router.laiers.local> In-Reply-To: <49726.192.168.4.151.1204973365.squirrel@router.laiers.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803091017.15485.hselasky@c2i.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Documentation on writing a custom socket X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2008 09:16:12 -0000 On Saturday 08 March 2008, Max Laier wrote: > Am Sa, 8.03.2008, 11:33, schrieb Hans Petter Selasky: > > I'm planning to create a new socket type in FreeBSD called AF_Q921, which > > is > > to be used for ISDN telephony. Where do I find documentation on how to > > interesting ... can you share more information on this project? Hi Max, I'm currently working on some redesign of my ISDN4BSD stack in cooperation with the FreeSwitch project. One of things that I want to do is to have all ISDN adapters appear like network devices. The ISDN protocols usually use something called Q.921 which is similar to TCP, only very simplified. The Q.931 part will either be in userland or in the kernel, and is used to do the telephony signalling like SETUP, CONNECT and RELEASE_COMPLETE. The idea is that once you use a socket you can easily change the layer2 to TCP, SCTP, UDP or whatever to be able to run Q.931 accross ethernet. --HPS Current I4B homepage: http://www.selasky.org/hans_petter/isdn4bsd