From owner-freebsd-isdn Thu Sep 3 11:53:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29829 for freebsd-isdn-outgoing; Thu, 3 Sep 1998 11:53:11 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from onizuka.vmunix.org (onizuka.vmunix.org [194.97.84.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29823 for ; Thu, 3 Sep 1998 11:53:07 -0700 (PDT) (envelope-from torstenb@vmunix.org) Received: by onizuka.vmunix.org via sendmail with stdio id for ; Thu, 3 Sep 1998 20:52:05 +0200 (CEST) Message-Id: Date: Thu, 3 Sep 1998 20:52:05 +0200 (CEST) From: torstenb@vmunix.org (Torsten Blum) To: leo@wau.mis.ah.nl Subject: Re: called-back, rejects and auto hangup Cc: freebsd-isdn@FreeBSD.ORG References: <19980902220352.22500@wau.mis.ah.nl> <19980903162118.27170@wau.mis.ah.nl> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In freebsd-isdn you write: >> 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? There are point-to-point and point-to-multipoint isdn lines. (the German Telekom calls them "Anlagenanschluss" and "Mehrgeraeteanschluss") The first one only supports one ISDN terminal equipment (phone, router, TA, isdn card etc) while a point-to-multipoint line supports up to 8 TE's. When a incomming call is arrives on a isdn point-to-multipoint line, all connected ISDN TE's are informed about the call. When an TE rejects the call ("call rejected", "user busy" etc) it's still possible for other TE's to accept the call. So the isdn switch has to wait till all remaining TE's signalled the switch wether they want to accept the call or not. If there's no response from the other TE's, the call will be rejected. Imagine the case where two ISDN phones are connected to an ISDN line. The first one is in use, the other one is free. When an incomming call arrives, the first ISDN phone will reject the call with "user busy", but the second one can still accept the call. On a point-to-point line you don't have this problem - since there is only one ISDN equipment and a reject will take affect immediately. Well, this applies to euro isdn. Dunno about ISDN in the US, but that's not what we're talking about. It's too different compared to what we have here in europe ;-) >> 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. No, this is not the only help, it's not even acceptable - IMHO. ISDN equipment that supports "ISDN callback" has to life with those call collisions. More than 5 years ago we already used ISDN-callback here in germany - with different "router packages" for DOS (KA9Q with ISDN drivers and other, custom made, software) for example. It's quite interesting to see that esp. ISDN-routers from the US (Ascend Pipeline/Max) can't handle this. There are other ISDN routers (Bintec for example) which do not have any problem with call collisions during isdn-callback. I work this this equipment every day and have some equipment at home and access to even more equipment at work. If anyone (Helmuth ?) want's to test isdn callback (or anything else), I'm more than happy to provide access to the equipment. -tb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message