From owner-freebsd-isdn@FreeBSD.ORG Fri Apr 15 09:33:10 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D336916A4CE for ; Fri, 15 Apr 2005 09:33:10 +0000 (GMT) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 782D643D4C for ; Fri, 15 Apr 2005 09:33:09 +0000 (GMT) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.13.1/8.12.10) with ESMTP id j3F9X66N025599 for ; Fri, 15 Apr 2005 11:33:07 +0200 (CEST) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.13.1/8.12.10/Submit) id j3F9X6tn025598 for freebsd-isdn@freebsd.org; Fri, 15 Apr 2005 11:33:06 +0200 (CEST) (envelope-from kuku) Date: Fri, 15 Apr 2005 11:33:06 +0200 (CEST) From: Christoph Kukulies Message-Id: <200504150933.j3F9X6tn025598@www.kukulies.org> To: freebsd-isdn@freebsd.org Subject: faked caller number? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 09:33:10 -0000 I'm wondering why my outgoing ISDN number is causing incoming calls on another ISDN phonenumber while I definitely know that I'm not calling this number (since I don't know that number at all). The owner of that number came to me and asked me why I was calling him. I wondered. Is there a way to fake the outgoing caller phone number (with i4B) or some other ISDN software? -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org From owner-freebsd-isdn@FreeBSD.ORG Fri Apr 15 09:45:24 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2054B16A4CE for ; Fri, 15 Apr 2005 09:45:24 +0000 (GMT) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 295EE43D62 for ; Fri, 15 Apr 2005 09:45:23 +0000 (GMT) (envelope-from is@beverly.kleinbus.org) Received: from fwd30.aul.t-online.de by mailout10.sul.t-online.com with smtp id 1DMNO5-0001Zo-07; Fri, 15 Apr 2005 11:45:21 +0200 Received: from beverly.kleinbus.org (E3ZtPGZboef8sxkd267KKccVSLXAEFHIFJnFQSiYOY-Mu2UlZwlw4L@[217.95.191.210]) by fwd30.sul.t-online.de with esmtp id 1DMNNz-0w2h3A0; Fri, 15 Apr 2005 11:45:15 +0200 Received: by beverly.kleinbus.org (Postfix, from userid 1501) id 9D779E8D1; Fri, 15 Apr 2005 11:44:19 +0200 (CEST) Date: Fri, 15 Apr 2005 11:44:18 +0200 From: Ignatios Souvatzis To: Christoph Kukulies Message-ID: <20050415094418.GA1260@beverly.kleinbus.org> References: <200504150933.j3F9X6tn025598@www.kukulies.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200504150933.j3F9X6tn025598@www.kukulies.org> User-Agent: Mutt/1.4.2i X-ID: E3ZtPGZboef8sxkd267KKccVSLXAEFHIFJnFQSiYOY-Mu2UlZwlw4L@t-dialin.net X-TOI-MSGID: df07fd4f-f93f-4a15-beda-1381101058cc cc: freebsd-isdn@freebsd.org Subject: Re: faked caller number? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 09:45:24 -0000 On Fri, Apr 15, 2005 at 11:33:06AM +0200, Christoph Kukulies wrote: > I'm wondering why my outgoing ISDN number is causing incoming > calls on another ISDN phonenumber while I definitely > know that I'm not calling this number (since I don't know that number at all). > > The owner of that number came to me and asked me why I was calling him. > I wondered. > > Is there a way to fake the outgoing caller phone number (with i4B) or some > other ISDN software? Most probably a number you did call (say, C) is call forwarding to that other number. If this is done by the telephone provider, instead of by initiating an outgoing call and connecting the data paths, your number will still appear as the originating one. You should compare your clocks, then compare your call log files. Less likely: Somebody with a Provider License is calling them faking to be you, either due to malice, or due to a typo. Those people are normally: - telephone service providers - 0800 number owners who want the 0800 number to appear on your display etc. Another possibility: some country prefix isn't transferred correctly, and it isn't you, but $someothercountryprefix+yournumber that is calling them. Regards, -is From owner-freebsd-isdn@FreeBSD.ORG Fri Apr 15 09:48:36 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F3DC16A4CF for ; Fri, 15 Apr 2005 09:48:36 +0000 (GMT) Received: from mail.duskware.de (mail.duskware.de [213.146.108.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 992B043D55 for ; Fri, 15 Apr 2005 09:48:35 +0000 (GMT) (envelope-from martin@duskware.de) Received: by mail.duskware.de (Postfix, from userid 205) id B7E9433A83; Fri, 15 Apr 2005 11:48:33 +0200 (CEST) Date: Fri, 15 Apr 2005 11:48:33 +0200 From: Martin Husemann To: Christoph Kukulies Message-ID: <20050415094833.GD29807@drowsy.duskware.de> References: <200504150933.j3F9X6tn025598@www.kukulies.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200504150933.j3F9X6tn025598@www.kukulies.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-isdn@freebsd.org Subject: Re: faked caller number? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 09:48:36 -0000 On Fri, Apr 15, 2005 at 11:33:06AM +0200, Christoph Kukulies wrote: > Is there a way to fake the outgoing caller phone number (with i4B) or some > other ISDN software? Not for "normal" ISDN connections - the exchange will screen and kill wrong outgoing numbers. Martin From owner-freebsd-isdn@FreeBSD.ORG Fri Apr 15 10:31:34 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DCAD16A4CE for ; Fri, 15 Apr 2005 10:31:34 +0000 (GMT) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B53543D49 for ; Fri, 15 Apr 2005 10:31:33 +0000 (GMT) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.13.1/8.12.10) with ESMTP id j3FAVRDH026680; Fri, 15 Apr 2005 12:31:28 +0200 (CEST) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.13.1/8.12.10/Submit) id j3FAVRdb026675; Fri, 15 Apr 2005 12:31:27 +0200 (CEST) (envelope-from kuku) Date: Fri, 15 Apr 2005 12:31:26 +0200 From: "Christoph P. Kukulies" To: Martin Husemann Message-ID: <20050415103126.GA26593@kukulies.org> References: <200504150933.j3F9X6tn025598@www.kukulies.org> <20050415094833.GD29807@drowsy.duskware.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050415094833.GD29807@drowsy.duskware.de> User-Agent: Mutt/1.4.1i cc: Christoph Kukulies cc: freebsd-isdn@freebsd.org Subject: Re: faked caller number? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 10:31:34 -0000 On Fri, Apr 15, 2005 at 11:48:33AM +0200, Martin Husemann wrote: > On Fri, Apr 15, 2005 at 11:33:06AM +0200, Christoph Kukulies wrote: > > Is there a way to fake the outgoing caller phone number (with i4B) or some > > other ISDN software? > > Not for "normal" ISDN connections - the exchange will screen and kill > wrong outgoing numbers. False alarm. Turned out that it wasn't a malign attempt. The caller was a friendly site who had misconfigured the outgoing MSN in his Windows NT PC. Thanks. -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org From owner-freebsd-isdn@FreeBSD.ORG Fri Apr 15 16:46:18 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A05B816A4CE for ; Fri, 15 Apr 2005 16:46:18 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9311F43D31 for ; Fri, 15 Apr 2005 16:46:17 +0000 (GMT) (envelope-from mailinglists@lebawuaschtbrezn.net) Received: from pD9E0A6F9.dip.t-dialin.net[217.224.166.249] (helo=[10.10.0.44]) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0MKwtQ-1DMTxQ2ZSf-0001ny; Fri, 15 Apr 2005 18:46:16 +0200 Message-ID: <425FEFD7.7080305@lebawuaschtbrezn.net> Date: Fri, 15 Apr 2005 18:46:15 +0200 From: Christoph Hoenig User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-isdn@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:a1600c91284085f640e1473606990b3e Subject: unable to trace B channel X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 16:46:18 -0000 Hi, I installed 5.3-release in order to trace the b channel with isdntrace in analyze mode. Unfortunately I was only able to trace the incoming and outgoing D channel data. # isdntrace -a -b -d -B Althoug I supplied the necessary -b switch no B Channel data is recorded. When turning off the D channel trace like in the command above (-d), the size of the binary dump is always 0Kb. With the documentation in mind I thought something was wrong about the i4brbch device. But at boot time everything seems to work quite well: kernel: isic0: [GIANT-LOCKED] kernel: isic0 at port 0xb00-0xb1f,0x300-0x31f,0x1300-0x131f,0xee0-0xeff,0x6e0-0x6ff,0x16e0-0x16ff,0x1b00-0x1b1f irq 10 flags 0x4 on isa0 kernel: isic0: passive stack unit 0 kernel: isic0: AVM A1 or Fritz!Card Classic kernel: isic1: [GIANT-LOCKED] kernel: isic1 at port 0xa40-0xa5f,0x240-0x25f,0x1240-0x125f,0xe20-0xe3f,0x620-0x63f,0x1620-0x163f,0x1a40-0x1a5f irq 11 flags 0x4 on isa0 kernel: isic1: passive stack unit 1 kernel: isic1: AVM A1 or Fritz!Card Classic kernel: i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) kernel: i4bctl: ISDN system control port attached kernel: i4brbch: 4 raw B channel access device(s) attached kernel: i4bisppp: 4 ISDN SyncPPP device(s) attached kernel: i4b: ISDN call control device attached kernel: i4btel: 4 ISDN telephony interface device(s) attached kernel: i4btrc: 4 ISDN trace device(s) attached The irqs used by my 2 non-PnP ISA Cards (AVM Fritz!) are reserved for isa slot use in the bios. I also tried to take a look at the debug ouput printed to the screen after a `isdndebug -m`. I don't really understand the ouput but at least I didn't found anything that looked like an error. Would be grateful to hear about things I can try, as the i4b doc, FAQ, Google and mailinglist archive didn't help on solving my problem. Christoph From owner-freebsd-isdn@FreeBSD.ORG Fri Apr 15 21:56:31 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DBA516A4CE for ; Fri, 15 Apr 2005 21:56:31 +0000 (GMT) Received: from swip.net (mailfe10.swipnet.se [212.247.155.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3328743D2D for ; Fri, 15 Apr 2005 21:56:30 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-216-36-54.daxnet.no ([193.216.36.54] verified) by mailfe10.swip.net (CommuniGate Pro SMTP 4.2.9) with ESMTP id 135737520; Fri, 15 Apr 2005 23:56:27 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Fri, 15 Apr 2005 23:57:30 +0200 User-Agent: KMail/1.7 References: <425FEFD7.7080305@lebawuaschtbrezn.net> In-Reply-To: <425FEFD7.7080305@lebawuaschtbrezn.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504152357.31866.hselasky@c2i.net> Subject: Re: unable to trace B channel X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 21:56:31 -0000 On Friday 15 April 2005 18:46, Christoph Hoenig wrote: > Hi, > > I installed 5.3-release in order to trace the b channel with isdntrace > in analyze mode. Unfortunately I was only able to trace the incoming and > outgoing D channel data. > > # isdntrace -a -b -d -B > > Althoug I supplied the necessary -b switch no B Channel data is > recorded. When turning off the D channel trace like in the command above > (-d), the size of the binary dump is always 0Kb. With the documentation > in mind I thought something was wrong about the i4brbch device. But at > boot time everything seems to work quite well: > > kernel: isic0: [GIANT-LOCKED] > kernel: isic0 at port > 0xb00-0xb1f,0x300-0x31f,0x1300-0x131f,0xee0-0xeff,0x6e0-0x6ff,0x16e0-0x16ff >,0x1b00-0x1b1f irq 10 flags 0x4 on isa0 > kernel: isic0: passive stack unit 0 > kernel: isic0: AVM A1 or Fritz!Card Classic > kernel: isic1: [GIANT-LOCKED] > kernel: isic1 at port > 0xa40-0xa5f,0x240-0x25f,0x1240-0x125f,0xe20-0xe3f,0x620-0x63f,0x1620-0x163f >,0x1a40-0x1a5f irq 11 flags 0x4 on isa0 > kernel: isic1: passive stack unit 1 > kernel: isic1: AVM A1 or Fritz!Card Classic > kernel: i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header > compression) > kernel: i4bctl: ISDN system control port attached > kernel: i4brbch: 4 raw B channel access device(s) attached > kernel: i4bisppp: 4 ISDN SyncPPP device(s) attached > kernel: i4b: ISDN call control device attached > kernel: i4btel: 4 ISDN telephony interface device(s) attached > kernel: i4btrc: 4 ISDN trace device(s) attached > > The irqs used by my 2 non-PnP ISA Cards (AVM Fritz!) are reserved for > isa slot use in the bios. I also tried to take a look at the debug ouput > printed to the screen after a `isdndebug -m`. I don't really understand > the ouput but at least I didn't found anything that looked like an error. > Would be grateful to hear about things I can try, as the i4b doc, FAQ, > Google and mailinglist archive didn't help on solving my problem. > > Christoph > Which of the two ISDN cards are you using? You might have to add "-u 1" to the options line. isdntrace does only trace for one unit at a time and it doesn't trace the B-channel unless isdnd and a connection is active on your ISDN card. --HPS From owner-freebsd-isdn@FreeBSD.ORG Sat Apr 16 02:56:41 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 064A216A4CE for ; Sat, 16 Apr 2005 02:56:41 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73A7343D2D for ; Sat, 16 Apr 2005 02:56:40 +0000 (GMT) (envelope-from mailinglists@lebawuaschtbrezn.net) Received: from [212.227.126.209] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1DMdU8-0005tP-00; Sat, 16 Apr 2005 04:56:40 +0200 Received: from [217.224.166.249] (helo=[10.10.0.44]) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1DMdU7-0004o2-00; Sat, 16 Apr 2005 04:56:39 +0200 Message-ID: <42607EE6.2030904@lebawuaschtbrezn.net> Date: Sat, 16 Apr 2005 04:56:38 +0200 From: Christoph Hoenig User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-isdn@freebsd.org References: <425FEFD7.7080305@lebawuaschtbrezn.net> <200504152357.31866.hselasky@c2i.net> In-Reply-To: <200504152357.31866.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:a1600c91284085f640e1473606990b3e Subject: Re: unable to trace B channel X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 02:56:41 -0000 Hans Petter Selasky wrote: >On Friday 15 April 2005 18:46, Christoph Hoenig wrote: > > >>Hi, >> >>I installed 5.3-release in order to trace the b channel with isdntrace >>in analyze mode. Unfortunately I was only able to trace the incoming and >>outgoing D channel data. >> >># isdntrace -a -b -d -B >> >>Althoug I supplied the necessary -b switch no B Channel data is >>recorded. When turning off the D channel trace like in the command above >>(-d), the size of the binary dump is always 0Kb. With the documentation >>in mind I thought something was wrong about the i4brbch device. But at >>boot time everything seems to work quite well: >> >>kernel: isic0: [GIANT-LOCKED] >>kernel: isic0 at port >>0xb00-0xb1f,0x300-0x31f,0x1300-0x131f,0xee0-0xeff,0x6e0-0x6ff,0x16e0-0x16ff >>,0x1b00-0x1b1f irq 10 flags 0x4 on isa0 >>kernel: isic0: passive stack unit 0 >>kernel: isic0: AVM A1 or Fritz!Card Classic >>kernel: isic1: [GIANT-LOCKED] >>kernel: isic1 at port >>0xa40-0xa5f,0x240-0x25f,0x1240-0x125f,0xe20-0xe3f,0x620-0x63f,0x1620-0x163f >>,0x1a40-0x1a5f irq 11 flags 0x4 on isa0 >>kernel: isic1: passive stack unit 1 >>kernel: isic1: AVM A1 or Fritz!Card Classic >>kernel: i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header >>compression) >>kernel: i4bctl: ISDN system control port attached >>kernel: i4brbch: 4 raw B channel access device(s) attached >>kernel: i4bisppp: 4 ISDN SyncPPP device(s) attached >>kernel: i4b: ISDN call control device attached >>kernel: i4btel: 4 ISDN telephony interface device(s) attached >>kernel: i4btrc: 4 ISDN trace device(s) attached >> >>The irqs used by my 2 non-PnP ISA Cards (AVM Fritz!) are reserved for >>isa slot use in the bios. I also tried to take a look at the debug ouput >>printed to the screen after a `isdndebug -m`. I don't really understand >>the ouput but at least I didn't found anything that looked like an error. >>Would be grateful to hear about things I can try, as the i4b doc, FAQ, >>Google and mailinglist archive didn't help on solving my problem. >> >>Christoph >> >> >> > >Which of the two ISDN cards are you using? You might have to add "-u 1" to the >options line. isdntrace does only trace for one unit at a time and it doesn't >trace the B-channel unless isdnd and a connection is active on your ISDN >card. > >--HPS > > > > I use both cards for tracing which is analyze mode ( described by http://people.freebsd.org/~hm/i4b-1001/node57.html ). Therefore I use the -R and -T switch for specifying the device insted of -u. However, in my setup this isn't necessary because the transmit an receive lines are connected to my cards like in the default configuration of isdntrace (receive on unit0 and transmit on unit1). Even when supplying -R 0 and -T 1 I still cannot dump B channel data (same applies to -R 1 and -T 0). Thanks anyway. Christoph From owner-freebsd-isdn@FreeBSD.ORG Sat Apr 16 16:38:20 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A09216A4CE for ; Sat, 16 Apr 2005 16:38:20 +0000 (GMT) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8461443D49 for ; Sat, 16 Apr 2005 16:38:19 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-200-252.daxnet.no ([193.217.200.252] verified) by mailfe02.swip.net (CommuniGate Pro SMTP 4.2.9) with ESMTP id 344608825; Sat, 16 Apr 2005 18:38:17 +0200 From: Hans Petter Selasky To: Christoph Hoenig Date: Sat, 16 Apr 2005 18:39:13 +0200 User-Agent: KMail/1.7 References: <425FEFD7.7080305@lebawuaschtbrezn.net> <200504152357.31866.hselasky@c2i.net> <42607EE6.2030904@lebawuaschtbrezn.net> In-Reply-To: <42607EE6.2030904@lebawuaschtbrezn.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200504161839.15630.hselasky@c2i.net> cc: freebsd-isdn@freebsd.org Subject: Re: unable to trace B channel X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 16:38:20 -0000 On Saturday 16 April 2005 04:56, Christoph Hoenig wrote: > Hans Petter Selasky wrote: > >On Friday 15 April 2005 18:46, Christoph Hoenig wrote: > >>Hi, > >> > >>I installed 5.3-release in order to trace the b channel with isdntrace > >>in analyze mode. Unfortunately I was only able to trace the incoming and > >>outgoing D channel data. > >> > >># isdntrace -a -b -d -B > >> > >>Althoug I supplied the necessary -b switch no B Channel data is > >>recorded. When turning off the D channel trace like in the command above > >>(-d), the size of the binary dump is always 0Kb. With the documentation > >>in mind I thought something was wrong about the i4brbch device. But at > >>boot time everything seems to work quite well: > >> > >>kernel: isic0: [GIANT-LOCKED] > >>kernel: isic0 at port > >>0xb00-0xb1f,0x300-0x31f,0x1300-0x131f,0xee0-0xeff,0x6e0-0x6ff,0x16e0-0x16 > >>ff ,0x1b00-0x1b1f irq 10 flags 0x4 on isa0 > >>kernel: isic0: passive stack unit 0 > >>kernel: isic0: AVM A1 or Fritz!Card Classic > >>kernel: isic1: [GIANT-LOCKED] > >>kernel: isic1 at port > >>0xa40-0xa5f,0x240-0x25f,0x1240-0x125f,0xe20-0xe3f,0x620-0x63f,0x1620-0x16 > >>3f ,0x1a40-0x1a5f irq 11 flags 0x4 on isa0 > >>kernel: isic1: passive stack unit 1 > >>kernel: isic1: AVM A1 or Fritz!Card Classic > >>kernel: i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header > >>compression) > >>kernel: i4bctl: ISDN system control port attached > >>kernel: i4brbch: 4 raw B channel access device(s) attached > >>kernel: i4bisppp: 4 ISDN SyncPPP device(s) attached > >>kernel: i4b: ISDN call control device attached > >>kernel: i4btel: 4 ISDN telephony interface device(s) attached > >>kernel: i4btrc: 4 ISDN trace device(s) attached > >> > >>The irqs used by my 2 non-PnP ISA Cards (AVM Fritz!) are reserved for > >>isa slot use in the bios. I also tried to take a look at the debug ouput > >>printed to the screen after a `isdndebug -m`. I don't really understand > >>the ouput but at least I didn't found anything that looked like an error. > >>Would be grateful to hear about things I can try, as the i4b doc, FAQ, > >>Google and mailinglist archive didn't help on solving my problem. > >> > >>Christoph > > > >Which of the two ISDN cards are you using? You might have to add "-u 1" to > > the options line. isdntrace does only trace for one unit at a time and it > > doesn't trace the B-channel unless isdnd and a connection is active on > > your ISDN card. > > > I use both cards for tracing which is analyze mode ( described by > http://people.freebsd.org/~hm/i4b-1001/node57.html ). Therefore I use > the -R and -T switch for specifying the device insted of -u. However, in > my setup this isn't necessary because the transmit an receive lines are > connected to my cards like in the default configuration of isdntrace > (receive on unit0 and transmit on unit1). Even when supplying -R 0 and > -T 1 I still cannot dump B channel data (same applies to -R 1 and -T 0). > With the existing ISDN driver you cannot read or write to the B-channels unless isdnd has an active connection on that B-channel, but you can always trace the D-channel hence it is opened when isdnd is started. If you just want to "cat" or trace the B1/B2-channel(s) of the S0-bus, I have an ISDN driver that can do that, but I haven't got support for your ISDN card, though adding support for it shouldn't be too difficult. If you are interested in trying it out, please let me know. My ISDN driver requires FreeBSD 5.x/6.x. --HPS