Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Sep 1998 16:21:18 +0200
From:      Leo Weppelman <leo@wau.mis.ah.nl>
To:        hm@kts.org
Cc:        freebsd-isdn@FreeBSD.ORG
Subject:   Re: called-back, rejects and auto hangup
Message-ID:  <19980903162118.27170@wau.mis.ah.nl>
In-Reply-To: <m0zEVPR-00000GC@bert.kts.org> from "Hellmuth Michaelis" on 1998/09/03 11:10 %2B0200
References:  <19980902220352.22500@wau.mis.ah.nl> <m0zEVPR-00000GC@bert.kts.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980903162118.27170>