From owner-freebsd-isdn Thu Sep 3 07:22:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22396 for freebsd-isdn-outgoing; Thu, 3 Sep 1998 07:22:30 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mailhost.ah.nl (ahns.mis.ah.nl [141.93.32.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA22377 for ; Thu, 3 Sep 1998 07:22:27 -0700 (PDT) (envelope-from leo@x1c19e02.wau.mis.ah.nl) Received: from leobsd.wau.mis.ah.nl(x1c19e02.wau.mis.ah.nl[141.93.34.7]) (3116 bytes) by mailhost.ah.nl via sendmail with P:esmtp/R:inet_bind/T:smtp (sender: ) id for ; Thu, 3 Sep 1998 16:25:52 +0200 (MZT) (Smail-3.2.0.99 1997-Dec-4 #5 built 1998-Jul-18) Received: (from leo@localhost) by leobsd.wau.mis.ah.nl (8.8.8/8.6.12) id QAA29411; Thu, 3 Sep 1998 16:21:18 +0200 (CEST) Message-ID: <19980903162118.27170@wau.mis.ah.nl> Date: Thu, 3 Sep 1998 16:21:18 +0200 From: Leo Weppelman To: hm@kts.org Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: called-back, rejects and auto hangup References: <19980902220352.22500@wau.mis.ah.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: from "Hellmuth Michaelis" on 1998/09/03 11:10 +0200 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu 03 Sep 1998, Hellmuth Michaelis wrote: > > I think Gary said it already: the remote calls back almost immediately; long > before the local call to the remote is disconnected - this can be seen > from the traces you sent me in private mail. Can you tell me why you think this is the case? > This situation is not being handled by isdnd due to internal design > limitations - changing this will be a major undertaking. > > The only help for this situation is, to delay the callback from the remote > for a time it takes to disconnect the local to the remote. > > If the remote were a i4b machine, i'd say "increase the callbackwait entry > parameter for this call to the time it takes to disconnect the local out- > going call". I'm quite shure (this was a Linux machine IIRC) that i4l has > something similar to tune the delay time; this it the knob to tune for this > situation. Yes, this was a Linux machine and, to reply partially to Martin, I cannot 'snoop' the isdn line from a separate machine :-( I increased the callback-delay parameter from 2 to 20 seconds. This did not change anything on my side. I still don't get the DISCONNECT within a minute. The (shortened) linux side trace looks like: 15:55:12 1998 Q.931 frame network->user broadcast 15:55:12 1998 callref 1 caller size 37 message type SETUP 15:55:12 1998 Q.931 frame user->network tei 80 15:55:12 1998 callref 1 called size 4 message type ALERTING 15:55:12 1998 Q.931 frame user->network tei 80 15:55:12 1998 callref 1 called size 8 message type DISCONNECT 15:55:12 1998 Cause 15:55:12 1998 coding 00 location 0000 15:55:12 1998 cause value 15 : Call rejected 15:55:12 1998 Q.931 frame network->user tei 80 15:55:12 1998 callref 1 caller size 4 message type RELEASE 15:55:12 1998 Q.931 frame user->network tei 80 15:55:12 1998 callref 1 called size 4 message type RELEASE COMPLETE 15:55:28 1998 Q.931 frame user->network tei 80 15:55:28 1998 callref 84 caller size 39 message type SETUP etc.... As you can see, the remote side waits +/- 16 seconds before starting the callback. In this time, my end gets no disconnect messages.... It looks like a bug somewhere indeed. The more because the alert shows up rather promptly at my end. The disconnect disappears somewhere in space.... Leo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message