From owner-freebsd-isdn@FreeBSD.ORG Mon Nov 12 20:49:49 2012 Return-Path: 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 785F9F6A for ; Mon, 12 Nov 2012 20:49:49 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id 274F38FC1A for ; Mon, 12 Nov 2012 20:49:48 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.hvnu.psconsult.nl [46.44.189.154]) by mx1.psconsult.nl (8.14.5/8.14.4) with ESMTP id qACKngUf017740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 12 Nov 2012 21:49:47 +0100 (CET) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.5/8.14.4/Submit) id qACKngrb017739 for freebsd-isdn@freebsd.org; Mon, 12 Nov 2012 21:49:42 +0100 (CET) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Mon, 12 Nov 2012 21:49:42 +0100 From: Paul Schenkeveld To: freebsd-isdn@freebsd.org Subject: Re: ISDN4BSD (HPS version) is going into ports Message-ID: <20121112204941.GA17627@psconsult.nl> References: <509E87EF.9070607@incore.de> <201211112246.44683.hselasky@c2i.net> <20121112102332.GA13575@psconsult.nl> <201211121458.01139.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201211121458.01139.hselasky@c2i.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 20:49:49 -0000 On Mon, Nov 12, 2012 at 02:58:01PM +0100, Hans Petter Selasky wrote: > Hi, > > I looks like this is a problem on 1.8.x only. I have a 1.6.x system bridging > to SIP and more and I don't see lots of unref'ed structures. > > It appears to me that the Asterisk API has changed, and now needs a final de- > ref, by the allocator of the call structure. Could you try this patch, on a > non-production system and see what happens: I don't have a non-production system with ISDN installed atm, will try and get hold of one for testing. With kind regards, Paul Schenkeveld