From owner-freebsd-isdn Mon Jan 1 14:40:56 2001 From owner-freebsd-isdn@FreeBSD.ORG Mon Jan 1 14:40:53 2001 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx-out.daemonmail.net (mx-out.daemonmail.net [209.75.5.3]) by hub.freebsd.org (Postfix) with ESMTP id A807737B400 for ; Mon, 1 Jan 2001 14:40:53 -0800 (PST) Received: from mx0.emailqueue.net (localhost.daemonmail.net [127.0.0.1]) by mx-out.daemonmail.net (8.9.3/8.9.3) with SMTP id OAA19300; Mon, 1 Jan 2001 14:40:44 -0800 (PST) (envelope-from kkonstan@webdaemon.net) Received: from webdaemon.net (webdaemon.net [193.92.210.14]) by mail.webdaemon.net with ESMTP id 2150Y5B2 Mon, 01 Jan 2001 14:40:41 -0700 (PST) Sender: kkonstan@mx-out.daemonmail.net Message-ID: <3A510768.689CCCB@webdaemon.net> Date: Tue, 02 Jan 2001 00:40:40 +0200 From: Konstantinos Konstantinidis Reply-To: kkonstan@duth.gr Organization: I've heard of it. X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en, el MIME-Version: 1.0 To: hm@hcs.de Cc: freebsd-isdn@freebsd.org Subject: Re: Bundling with i4b References: <20010101102015.389402B7@hcswork.hcs.de> Content-Type: text/plain; charset=iso-8859-7 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellmuth Michaelis wrote: > > >From the keyboard of Konstantinos Konstantinidis: > > > > It shouldn't be hard to add this functionality, but I tried to do it and > > failed miserably since I don't know my way around the i4b source tree. > > Perhaps someone could consider making this minor change or point out to > > me a good place to start in the source tree. > > This seems to be a bug in isdnd. Incoming calls are handled in the file > msghdl.c, function msg_connect_ind(). This is the place where incoming > calls are checked whether to answer them or to ignore them. All the > checking of the little pieces is done in file support.c function > find_matching_entry_incoming() which is called from msg_connect_ind(). Thanks a lot for the pointers, they really helped. Apparently this behaviour is only triggered if the dialouttype is 'calledback', so I changed my config and now that it is 'normal' the problem is solved (the calls are ignored). I can use normal because I can't call the cisco to call me back anyway, but it's on our phone network so it's free to leave the connection up permanently. However, for real callback circumstances the problem (if it really is a problem, after all the correct thing to do would be to configure the cisco apropriately) might persist. Here's the offending snippet for reference: if (cep->dialin_reaction == REACT_ACCEPT && cep->dialouttype == DIALOUT_CALLEDBACK) [accept incoming call for callback in progress] I can't say I understand fully the mechanisms of the callback implemented, but I'd hazard a guess that the above should only happen while we're actually waiting for a callback, like this: if (cep->dialin_reaction == REACT_ACCEPT && cep->dialouttype == DIALOUT_CALLEDBACK && cep->status == ST_PCB_WAITCALL) [accept incoming call for callback in progress] I have no means of testing this however, it might break callback support entirely or introduce a race condition for all I know - perhaps someone else might be interested in pursuing this further. Thanks again, K. Konstantinidis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message