From owner-freebsd-isdn Mon Aug 31 02:22:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17911 for freebsd-isdn-outgoing; Mon, 31 Aug 1998 02:22:14 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17856 for ; Mon, 31 Aug 1998 02:21:56 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id LAA04145 for freebsd-isdn@freebsd.org; Mon, 31 Aug 1998 11:20:57 +0200 (MEST) (envelope-from kuku) Date: Mon, 31 Aug 1998 11:20:57 +0200 (MEST) From: Christoph Kukulies Message-Id: <199808310920.LAA04145@gilberto.physik.RWTH-Aachen.DE> To: freebsd-isdn@FreeBSD.ORG Subject: monitoring calls Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org bisdn had the 'feature' to log also incoming connections on the S0 bus that were not destined to the host running bisdn, i.e. I could see from the log file or the logging ttyvx that another source has dialed in thus finding the cause when two channels were already busy. How can I configure (without large logging overhead) find out in isdn4bsd what numbers were dialing in on the bus? And better yet, to throw up an ever lasting question: Where is the entry point to build some channel monitoring, e.g. what channels are busy, if they are dial in /out, what sort of service is being active and what phone number is related to them. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message