From owner-freebsd-isdn Fri Aug 28 12:33:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06308 for freebsd-isdn-outgoing; Fri, 28 Aug 1998 12:33:10 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06291 for ; Fri, 28 Aug 1998 12:33:02 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id VAA18605; Fri, 28 Aug 1998 21:32:01 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0zCUFd-002ZjZC; Fri, 28 Aug 98 21:32 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Fri, 28 Aug 1998 21:10:51 +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; Fri, 28 Aug 1998 21:10:51 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #2 built 1998-Aug-25) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: ISDN features In-Reply-To: <19980828194214.51063@foobar.franken.de> from Harold Gutch at "Aug 28, 98 07:42:14 pm" To: logix@foobar.franken.de (Harold Gutch) Date: Fri, 28 Aug 1998 21:10:51 +0200 (CEST) Cc: freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL40 (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 Harold Gutch wrote: > ISDN (or is it only DSS-1 ?) has a couple of features like > automatically calling the other side as soon as their line is > free. > isdn4bsd doesn't seem to be able to parse these call-requests > coming in on the S0-bus: This is true. It is very difficult, time consuming and expensive in terms of being charged by the local PTT to write and debug code to decode this type of messages (which i did partially to get AOCD and AOCE decoded) and this is the cause isdn4bsd is not able to decode them. More, i don't see any advantage i get if i would be able to decode those messages (there are a few conditions, why CCBS - Completition of Call to Busy Subscriber - is only possible between some selected - but growing - number of users). But - as usual - i'll happily accept diffs if someone likes to decode those messages! (btw: in case someone likes to know what they are, there is a web-based ISDN message decoder at http://www.ch.engelschall.com/u/martin/webdecoder/webdecoder.cgi nice !) > Aug 28 19:26:39 foobar /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for > cr = 0x0, crflag = 0x0, msg = 0x62, frame = 0x62 0x1c 0x33 0x91 0xa1 0x30 0x2 0x2 0x40 ^^^^^^^^^^^^^^^^^^^^^^ These messages have either a global or dummy call reference, these type of messages should not being displayed anymore by recent i4b versions (i don't recall when i changed this). > I dont really mind seeing these messages, but shouldnt i4b rather > correctly interprete these messages and print out some > appropriate info ? No, see above. > Or is this just my setup ? :) No. > The above just was an example, i guess there are a couple of > other ISDN-features that isdn4bsd doesnt know of. There are many, many features isdn4bsd has not the slightest idea of. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe A duck is like a bicycle because they both have two wheels except the duck (terry@cs.weber.edu) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message