From owner-freebsd-isdn Tue Apr 7 03:25:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02434 for freebsd-isdn-outgoing; Tue, 7 Apr 1998 03:25:08 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from casparc.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA02403 for ; Tue, 7 Apr 1998 03:25:03 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0yMUq8-00298sC; Tue, 7 Apr 98 11:38 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Tue, 7 Apr 1998 11:11:41 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for freebsd-isdn@freebsd.org; Tue, 7 Apr 1998 11:08:48 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #7 built 1997-Jul-4) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: Callback with i4b In-Reply-To: <199804062254.AAA00904@peedub.muc.de> from Gary Jennejohn at "Apr 7, 98 00:54:36 am" To: freebsd-isdn@FreeBSD.ORG (ISDN for BSD) Date: Tue, 7 Apr 1998 11:08:48 +0200 (CEST) Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gary Jennejohn wrote: > > - isdnd is currently no able to handle simultaneous callins and > > callouts (the callout for a callback destination goes out on > > one B channel and before this call is terminated the callback > > comes in on the other B channel). Changing isdnd to be able to > > handle this situation is non-trivial. > > > > this may also require some changes in the kernel. No, i don't think so. I've had a look to the problem, but gave up temporarily because so much work is required. The kernel handles this situation fine, the problems are the datastructures in isdnd: The struct cfg_entry needs to be split up in two parts, one part containing the static and dynamic configuration for one logical link or in terms of isdnd, config entry. The other (part[s]) will be the (temporary) characteristic(s) of one or more (!) ISDN connections for that configured logical link. One or more means, that it may be one connection in case of a "normal" call; two connections in case of a callback/calledback entry and more than two in case of (future) channel bonding operations. What is needed is some form of static config entry, which has the start address of a dynamically allocated linked list describing the actual ISDN connections being active for that entry. When you start to implement this (which i did, but then stopped as i realized, how much work this will be), you will soon come to the point, where all the isdnd cdid management routines have to be rewritten, and all the routines accessing the dynamic part of the current isdnd's config entries. > I'm willing to look > into getting this working (I looked at a few months ago and still have a > vague idea what's needed), unless someone else *really* wants to do it. No no, just go ahead ! :-)))) hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe "Those who can, do. Those who can't, talk. And those who can't talk, talk about talking." (B. Shaw) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message