From owner-freebsd-isdn Fri Aug 28 10:45:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22096 for freebsd-isdn-outgoing; Fri, 28 Aug 1998 10:45:04 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22085 for ; Fri, 28 Aug 1998 10:44:53 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id TAA06328; Fri, 28 Aug 1998 19:42:14 +0200 (CEST) Message-ID: <19980828194214.51063@foobar.franken.de> Date: Fri, 28 Aug 1998 19:42:14 +0200 From: Harold Gutch To: freebsd-isdn@FreeBSD.ORG Subject: ISDN features Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, 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: Aug 28 19:24:53 foobar /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x0, crflag = 0x0, msg = 0x62, frame = 0x62 0x1c 0x12 0x91 0xa1 0xf 0x2 0x2 0x40 0x91 0x6 0x6 0x4 0x0 0x82 0x67 0x1 0xa 0x2 0x1 0x3 0x70 0xa 0xa1 0x39 0x34 0x31 0x34 0x34 0x37 0x36 0x37 0x30 Aug 28 19:24:56 foobar /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x0, crflag = 0x0, msg = 0x62, frame = 0x62 0x1c 0x12 0x91 0xa1 0xf 0x2 0x2 0x40 0x91 0x6 0x6 0x4 0x0 0x82 0x67 0x1 0xa 0x2 0x1 0x1 0x70 0xa 0xa1 0x39 0x34 0x31 0x34 0x34 0x37 0x36 0x37 0x30 etc. being repeated until the other's side line is free and my phone (?) calls him: Aug 28 19:26:38 foobar /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x0, crflag = 0x0, msg = 0x62, frame = 0x62 0x1c 0x22 0x91 0xa1 0x1f 0x2 0x2 0x40 0x95 0x6 0x6 0x4 0x0 0x82 0x67 0x1 0x8 0x30 0x11 0xa 0x1 0x1 0x2 0x1 0x1 0x40 0x9 0x4 0x3 0x80 0x90 0xa3 0x7d 0x2 0x91 0x81 0x70 0xa 0xa1 0x39 0x34 0x31 0x34 0x34 0x37 0x36 0x37 0x30 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 0x96 0x6 0x6 0x4 0x0 0x82 0x67 0x1 0x6 0x30 0x22 0xa 0x1 0x1 0x2 0x1 0x1 0x30 0xf 0xa1 0xd 0xa 0x1 0x2 0x12 0x8 0x39 0x34 0x34 0x38 0x31 0x34 0x33 0x35 0x40 0x9 0x4 0x3 0x80 0x90 0xa3 0x7d 0x2 0x91 0x81 0x70 0xa 0xa1 0x39 0x34 0x31 0x34 0x34 0x37 0x36 0x37 0x30 At least i *guess* that these messages were caused by this "call-back" feature, as they appeared precisely at the same time as i made such a call. I dont really mind seeing these messages, but shouldnt i4b rather correctly interprete these messages and print out some appropriate info ? Or is this just my setup ? :) The above just was an example, i guess there are a couple of other ISDN-features that isdn4bsd doesnt know of. -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message