From owner-freebsd-isdn@FreeBSD.ORG  Sun Jan  7 10:16:14 2007
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
X-Original-To: freebsd-isdn@freebsd.org
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 97A1916A403
	for <freebsd-isdn@freebsd.org>; Sun,  7 Jan 2007 10:16:14 +0000 (UTC)
	(envelope-from maillist@ovb.ch)
Received: from ovbis01.ovb.ch (ovbis01.ovb.ch [213.188.32.144])
	by mx1.freebsd.org (Postfix) with ESMTP id 61C3F13C458
	for <freebsd-isdn@freebsd.org>; Sun,  7 Jan 2007 10:16:14 +0000 (UTC)
	(envelope-from maillist@ovb.ch)
Received: from ovbas00.ovb.ch ([213.180.173.192] helo=[192.168.30.100])
	by ovbis01.ovb.ch with esmtp (Exim 4.51)
	id 1H3V4U-000LSn-HO; Sun, 07 Jan 2007 11:16:10 +0100
Message-ID: <45A0C86F.5050104@ovb.ch>
Date: Sun, 07 Jan 2007 11:16:15 +0100
From: Oliver von Bueren <maillist@ovb.ch>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: freebsd-isdn@freebsd.org
References: <459FCD1E.9080303@ovb.ch> <web-51294860@mailbe05.swip.net>
	<45A012B3.9050809@ovb.ch> <web-54124816@mailbe03.swip.net>
In-Reply-To: <web-54124816@mailbe03.swip.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: ISDN4BSD - Dropped Calls
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
	<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
	<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jan 2007 10:16:14 -0000

Hi Hans Petter


Hans Petter wrote:
> Most ISDN equipment I have seen never queries for STATUS, whatsoever. 
> So maybe your provider did not see a reason to support that.
> > If I find anything, I'll keep you posted.
> > If you've any ideas on how to fix my problem, drop me a
> >note.
> I could implement an option that allows you to disable checking of 
> status, but I really don't like to do that.
[...]
> You can try putting:
> if (send_status_enquiry) {
>     newstate--;
> }
> Before:
> cd->state = newstate;
> That will prevent the status expiry timer from elapsing.
I've tested you suggestion and of course it worked. According to the 
trace, the STATUS_ENQUIRY is never answered by the PBX but as the timer 
doesn't expire, no disconnect is made.

I understand your point about not liking this workaround. But if you 
could add an option (isdnconfig ?) to switch it on/off would be great.

Thanks and have a nice weekend!

Oliver