From owner-freebsd-isdn Sat Apr 4 09:37:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16239 for freebsd-isdn-outgoing; Sat, 4 Apr 1998 09:37:10 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16232 for ; Sat, 4 Apr 1998 09:37:05 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id TAA03329; Sat, 4 Apr 1998 19:36:37 +0200 (CEST) Received: from localhost (blaz@localhost) by gold.amis.net (8.8.8/8.8.8) with SMTP id TAA00305; Sat, 4 Apr 1998 19:16:04 +0200 (CEST) Date: Sat, 4 Apr 1998 19:16:04 +0200 (CEST) From: Blaz Zupan To: Wolfgang Helbig cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Callback with i4b In-Reply-To: <199804041157.NAA01485@rvc1.informatik.ba-stuttgart.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Is anybody successfully using callback with i4b? I have a setup where I > It works fine with a bisdn machine calling back. Probably because the bisdn machine calls back immediately. My isdnd.rc is basically the same as Pouls. So the problem is probably caused by the Livingston which takes some time to call back and in the mean time (in *less* than a second) i4b decides that it needs to call again... > There seem to be some problems, it *both* i4b-machines are connected to > a PBX instead of directly to an NT from the telecom. In my case one side is connected to an NT and the other side is a Livingston PM3 on PRI. Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message