From owner-freebsd-isdn@freebsd.org Fri Feb 19 09:40:04 2016 Return-Path: Delivered-To: freebsd-isdn@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92150AACAAC for ; Fri, 19 Feb 2016 09:40:04 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 29DD71E16 for ; Fri, 19 Feb 2016 09:40:03 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id 9318F67AF9 for ; Fri, 19 Feb 2016 10:31:02 +0100 (CET) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id p8P4PyrmuFlS for ; Fri, 19 Feb 2016 10:31:00 +0100 (CET) Received: from mail.local.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id 89FE567ADE for ; Fri, 19 Feb 2016 10:31:00 +0100 (CET) Received: from bsdlo.incore (bsdlo.incore [192.168.0.84]) by mail.local.incore (Postfix) with ESMTP id 61CBF508A2 for ; Fri, 19 Feb 2016 10:31:00 +0100 (CET) Message-ID: <56C6E0D4.5060603@incore.de> Date: Fri, 19 Feb 2016 10:31:00 +0100 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: freebsd-isdn@freebsd.org Subject: chan_capi error after update Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 09:40:04 -0000 Hi, isdn4bsd + chan_capi works fine for years now, thanks !! On machines running FreeBSD 8.4-STABLE (LOSERVER) #2 r284338 with ihfc0: port 0xbc00-0xbc07 mem 0xff532000-0xff5320ff irq 22 at device 1.0 on pci6 ihfc0: [ITHREAD] ihfc0: Attaching I4B controller 0. ihfc0: Creating /dev/ihfc0.X. i4btel: 8 ISDN telephony interface device(s) attached i4btrc: 64 ISDN trace device(s) attached i4bctl: ISDN system control port attached i4b: ISDN call control device attached i4bisppp: 8 ISDN SyncPPP device(s) attached there is a problem after updating software (without changing configuration) asterisk18: 1.8.16.0 ---> 1.8.32.1 chan_capi: 2.0.3 ---> 2.0.14 libcapi: 2.0.1 ---> 2.0.2 isdn4bsd-kmod: 2.0.7 ---> 2.0.11 isdn4bsd-utils: 2.0.7 ---> 2.0.11 isdnd works fine, but chan_capi has a problem when asterisk starts: [2016-02-18 17:16:51.477] VERBOSE[8810] chan_capi.c: [2016-02-18 17:16:51.477] == Reading config for ISDN [2016-02-18 17:16:51.477] VERBOSE[8810] chan_capi.c: [2016-02-18 17:16:51.477] -- config entry 'ISDN' T=(4982871,isdn-in,2) C=[0,0] E=(0,4,64) G=(1.000000/1.000000) H=(0) [2016-02-18 17:16:51.477] ERROR[8810] chan_capi.c: CAPI error sending CAPI_FACILITY_REQ { header { WORD wLen = 0x0000 WORD wApp = 0xffff WORD wCmd = 0x8468 WORD wNum = 0x0001 DWORD dwCid = 0x00000000 } data { WORD wSelector = 0x0003 STRUCT Param.ptr = 0x03 '?', 0x00 '?', 0x00 '?', 0x00 '?'. } } (NCCI=0) (error=0x1101) [2016-02-18 17:16:51.477] NOTICE[8810] chan_capi.c: could not send FACILITY REQUEST! [2016-02-18 17:16:51.477] VERBOSE[8810] chan_capi.c: [2016-02-18 17:16:51.477] -- CAPI controller 0 supports: [DTMF][echo cancellation][supplementary] [2016-02-18 17:16:51.477] ERROR[8810] chan_capi.c: CAPI error sending CAPI_LISTEN_REQ { header { WORD wLen = 0x0000 WORD wApp = 0xffff WORD wCmd = 0x8462 WORD wNum = 0x0002 DWORD dwCid = 0x00000000 } data { DWORD dwInfoMask = 0x0000ffff DWORD dwCipMask1 = 0x1fff03ff DWORD dwCipMask2 = 0x00000000 STRUCT src_telno.ptr = (empty) STRUCT src_subaddr.ptr = (empty) } } (NCCI=0) (error=0x1101) [2016-02-18 17:16:51.477] ERROR[8810] chan_capi.c: Unable to listen on controller=0! [2016-02-18 17:16:51.478] VERBOSE[8810] channel.c: [2016-02-18 17:16:51.478] == Registered channel type 'CAPI' (Common ISDN API 2.0 Driver 2.0.14) [2016-02-18 17:16:51.478] VERBOSE[8810] pbx.c: [2016-02-18 17:16:51.478] == Registered application 'capiCommand' [2016-02-18 17:16:51.478] ERROR[8810] lock.c: chan_capi.c line 1237 (capi_application_usleep): mutex '&p_app->lock' freed more times than we've locked! [2016-02-18 17:16:51.478] VERBOSE[8810] loader.c: [2016-02-18 17:16:51.478] chan_capi.so => (Common ISDN API 2.0 Driver 2.0.14) [2016-02-18 17:16:51.478] ERROR[8810] lock.c: chan_capi.c line 1237 (capi_application_usleep): Error releasing mutex: Operation not permitted Some seconds later: [2016-02-18 17:16:51.527] VERBOSE[8810] asterisk.c: [2016-02-18 17:16:51.527] Asterisk Ready. [2016-02-18 17:16:53.873] VERBOSE[8810] chan_capi.c: [2016-02-18 17:16:53.873] -- CAPI controller 0 supports: [DTMF][echo cancellation][supplementary] [2016-02-18 17:16:55.258] VERBOSE[8810] chan_capi.c: [2016-02-18 17:16:55.258] -- listening on controller=0, cip_mask=0x1fff03ff [2016-02-18 17:16:55.258] WARNING[8810] chan_capi.c: CAPI application was restarted Any ideas ? Regards, Andreas Longwitz From owner-freebsd-isdn@freebsd.org Fri Feb 19 16:44:44 2016 Return-Path: Delivered-To: freebsd-isdn@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 881E2AAE44A for ; Fri, 19 Feb 2016 16:44:44 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 30BB719F1 for ; Fri, 19 Feb 2016 16:44:43 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 94A8F1FE023; Fri, 19 Feb 2016 17:44:34 +0100 (CET) Subject: Re: chan_capi error after update To: Andreas Longwitz , freebsd-isdn@freebsd.org References: <56C6E0D4.5060603@incore.de> From: Hans Petter Selasky Message-ID: <56C74704.6060606@selasky.org> Date: Fri, 19 Feb 2016 17:47:00 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56C6E0D4.5060603@incore.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 16:44:44 -0000 On 02/19/16 10:31, Andreas Longwitz wrote: > Hi, > > isdn4bsd + chan_capi works fine for years now, thanks !! > > On machines running > FreeBSD 8.4-STABLE (LOSERVER) #2 r284338 > with > ihfc0: port 0xbc00-0xbc07 mem > 0xff532000-0xff5320ff irq 22 at device 1.0 on pci6 > ihfc0: [ITHREAD] > ihfc0: Attaching I4B controller 0. > ihfc0: Creating /dev/ihfc0.X. > i4btel: 8 ISDN telephony interface device(s) attached > i4btrc: 64 ISDN trace device(s) attached > i4bctl: ISDN system control port attached > i4b: ISDN call control device attached > i4bisppp: 8 ISDN SyncPPP device(s) attached > > there is a problem after updating software (without changing configuration) > > asterisk18: 1.8.16.0 ---> 1.8.32.1 > chan_capi: 2.0.3 ---> 2.0.14 > libcapi: 2.0.1 ---> 2.0.2 > isdn4bsd-kmod: 2.0.7 ---> 2.0.11 > isdn4bsd-utils: 2.0.7 ---> 2.0.11 > > isdnd works fine, but chan_capi has a problem when asterisk starts: > > [2016-02-18 17:16:51.477] VERBOSE[8810] chan_capi.c: [2016-02-18 > 17:16:51.477] == Reading config for ISDN > [2016-02-18 17:16:51.477] VERBOSE[8810] chan_capi.c: [2016-02-18 > 17:16:51.477] -- config entry 'ISDN' T=(4982871,isdn-in,2) C=[0,0] > E=(0,4,64) G=(1.000000/1.000000) H=(0) > [2016-02-18 17:16:51.477] ERROR[8810] chan_capi.c: CAPI error sending > CAPI_FACILITY_REQ { > header { > WORD wLen = 0x0000 > WORD wApp = 0xffff > WORD wCmd = 0x8468 > WORD wNum = 0x0001 > DWORD dwCid = 0x00000000 > } > data { > WORD wSelector = 0x0003 > STRUCT Param.ptr = 0x03 '?', 0x00 '?', 0x00 '?', 0x00 '?'. > } > } > (NCCI=0) (error=0x1101) > [2016-02-18 17:16:51.477] NOTICE[8810] chan_capi.c: could not send > FACILITY REQUEST! > [2016-02-18 17:16:51.477] VERBOSE[8810] chan_capi.c: [2016-02-18 > 17:16:51.477] -- CAPI controller 0 supports: [DTMF][echo > cancellation][supplementary] > [2016-02-18 17:16:51.477] ERROR[8810] chan_capi.c: CAPI error sending > CAPI_LISTEN_REQ { > header { > WORD wLen = 0x0000 > WORD wApp = 0xffff > WORD wCmd = 0x8462 > WORD wNum = 0x0002 > DWORD dwCid = 0x00000000 > } > data { > DWORD dwInfoMask = 0x0000ffff > DWORD dwCipMask1 = 0x1fff03ff > DWORD dwCipMask2 = 0x00000000 > STRUCT src_telno.ptr = (empty) > STRUCT src_subaddr.ptr = (empty) > } > } > (NCCI=0) (error=0x1101) > [2016-02-18 17:16:51.477] ERROR[8810] chan_capi.c: Unable to listen on > controller=0! > [2016-02-18 17:16:51.478] VERBOSE[8810] channel.c: [2016-02-18 > 17:16:51.478] == Registered channel type 'CAPI' (Common ISDN API 2.0 > Driver 2.0.14) > [2016-02-18 17:16:51.478] VERBOSE[8810] pbx.c: [2016-02-18 17:16:51.478] > == Registered application 'capiCommand' > [2016-02-18 17:16:51.478] ERROR[8810] lock.c: chan_capi.c line 1237 > (capi_application_usleep): mutex '&p_app->lock' freed more times than > we've locked! > [2016-02-18 17:16:51.478] VERBOSE[8810] loader.c: [2016-02-18 > 17:16:51.478] chan_capi.so => (Common ISDN API 2.0 Driver 2.0.14) > [2016-02-18 17:16:51.478] ERROR[8810] lock.c: chan_capi.c line 1237 > (capi_application_usleep): Error releasing mutex: Operation not permitted > > Some seconds later: > [2016-02-18 17:16:51.527] VERBOSE[8810] asterisk.c: [2016-02-18 > 17:16:51.527] Asterisk Ready. > [2016-02-18 17:16:53.873] VERBOSE[8810] chan_capi.c: [2016-02-18 > 17:16:53.873] -- CAPI controller 0 supports: [DTMF][echo > cancellation][supplementary] > [2016-02-18 17:16:55.258] VERBOSE[8810] chan_capi.c: [2016-02-18 > 17:16:55.258] -- listening on controller=0, cip_mask=0x1fff03ff > [2016-02-18 17:16:55.258] WARNING[8810] chan_capi.c: CAPI application > was restarted > > Any ideas ? Hi, Did you set the correct permissions for /dev/capi20. Maybe Asterisk is running it as a different user? --HPS From owner-freebsd-isdn@freebsd.org Fri Feb 19 20:52:30 2016 Return-Path: Delivered-To: freebsd-isdn@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E0E7AACC77 for ; Fri, 19 Feb 2016 20:52:30 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4970A1B9D for ; Fri, 19 Feb 2016 20:52:29 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id 3FAC467C15; Fri, 19 Feb 2016 21:52:27 +0100 (CET) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id KLJsCkc10iPW; Fri, 19 Feb 2016 21:52:26 +0100 (CET) Received: from mail.local.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id C3A3D67C13; Fri, 19 Feb 2016 21:52:26 +0100 (CET) Received: from bsdmhs.longwitz (unknown [192.168.99.6]) by mail.local.incore (Postfix) with ESMTP id 7364950899; Fri, 19 Feb 2016 21:52:26 +0100 (CET) Message-ID: <56C7808A.7060809@incore.de> Date: Fri, 19 Feb 2016 21:52:26 +0100 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Hans Petter Selasky , freebsd-isdn@freebsd.org Subject: Re: chan_capi error after update References: <56C6E0D4.5060603@incore.de> <56C74704.6060606@selasky.org> In-Reply-To: <56C74704.6060606@selasky.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 20:52:30 -0000 thanks for answer. > Did you set the correct permissions for /dev/capi20. Maybe Asterisk is > running it as a different user? > > --HPS Yes, in my startup script I have chown asterisk:wheel /dev/capi20 and ls -l /dev/capi20 gives crw------- 1 asterisk wheel 0, 162 18 Feb 17:16 /dev/capi20 Andreas Longwitz From owner-freebsd-isdn@freebsd.org Sat Feb 20 09:49:53 2016 Return-Path: Delivered-To: freebsd-isdn@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67C1AAADC28 for ; Sat, 20 Feb 2016 09:49:53 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 33649FEC for ; Sat, 20 Feb 2016 09:49:52 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 346951FE023; Sat, 20 Feb 2016 10:49:51 +0100 (CET) Subject: Re: chan_capi error after update To: Andreas Longwitz , freebsd-isdn@freebsd.org References: <56C6E0D4.5060603@incore.de> <56C74704.6060606@selasky.org> From: Hans Petter Selasky Message-ID: <56C83752.6080708@selasky.org> Date: Sat, 20 Feb 2016 10:52:18 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56C74704.6060606@selasky.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Feb 2016 09:49:53 -0000 On 02/19/16 17:47, Hans Petter Selasky wrote: > [2016-02-18 17:16:51.478] VERBOSE[8810] pbx.c: [2016-02-18 17:16:51.478] > == Registered application 'capiCommand' > [2016-02-18 17:16:51.478] ERROR[8810] lock.c: chan_capi.c line 1237 > (capi_application_usleep): mutex '&p_app->lock' freed more times than > we've locked! Hi, I found a minor bug there. I've made v2.0.15 available. Just SVN up and install the port. I've also fixed a build issue with later versions of asterisk, that it needs the "-fblocks" CFLAG when compiling. I'm currently using the exact same setup with Asterisk 11.x without any such problems. --HPS From owner-freebsd-isdn@freebsd.org Sat Feb 20 14:13:51 2016 Return-Path: Delivered-To: freebsd-isdn@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4B3CAAE4AE for ; Sat, 20 Feb 2016 14:13:51 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A86515DF for ; Sat, 20 Feb 2016 14:13:50 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id 53DE667AA7; Sat, 20 Feb 2016 15:13:42 +0100 (CET) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id dlnh4pH4RpKn; Sat, 20 Feb 2016 15:13:41 +0100 (CET) Received: from mail.local.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id 3320C67A78; Sat, 20 Feb 2016 15:13:41 +0100 (CET) Received: from bsdmhs.longwitz (unknown [192.168.99.6]) by mail.local.incore (Postfix) with ESMTP id 7C5E550899; Sat, 20 Feb 2016 15:13:40 +0100 (CET) Message-ID: <56C87494.6020605@incore.de> Date: Sat, 20 Feb 2016 15:13:40 +0100 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Hans Petter Selasky CC: freebsd-isdn@freebsd.org Subject: Re: chan_capi error after update References: <56C6E0D4.5060603@incore.de> <56C74704.6060606@selasky.org> <56C83752.6080708@selasky.org> In-Reply-To: <56C83752.6080708@selasky.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Feb 2016 14:13:51 -0000 Hi, thanks for investigating in this problem ! > I found a minor bug there. I've made v2.0.15 available. Just SVN up and > install the port. I've also fixed a build issue with later versions of > asterisk, that it needs the "-fblocks" CFLAG when compiling. > > I'm currently using the exact same setup with Asterisk 11.x without any > such problems. OK, at the moment I am a little bit late with versions because I use a consistent portstree 2014Q4 running poudriere on all of my servers. > > --HPS After update to chan_capi 2.0.15 (without the -fblocks CFLAG, because the compiler does not know in V8: cc1: error: unrecognized command line option "-fblocks") the problem has not gone away. But the order of the messages is a little bit different now: [2016-02-20 14:55:37.071] VERBOSE[21261] config.c: [2016-02-20 14:55:37.071] == Parsing '/usr/local/etc/asterisk/capi.conf': [2016-02-20 14:55:37 .072] VERBOSE[21261] config.c: [2016-02-20 14:55:37.072] == Found [2016-02-20 14:55:37.072] VERBOSE[21261] chan_capi.c: [2016-02-20 14:55:37.072] == Reading config for ISDN [2016-02-20 14:55:37.072] VERBOSE[21261] chan_capi.c: [2016-02-20 14:55:37.072] -- config entry 'ISDN' T=(4982871,isdn-in,2) C=[0,0] E=(0,4,64) G=(1.000000/1.000000) H=(0) [2016-02-20 14:55:37.073] ERROR[21261] chan_capi.c: CAPI error sending CAPI_FACILITY_REQ { header { WORD wLen = 0x0000 WORD wApp = 0xffff WORD wCmd = 0x8468 WORD wNum = 0x0001 DWORD dwCid = 0x00000000 } data { WORD wSelector = 0x0003 STRUCT Param.ptr = 0x03 '?', 0x00 '?', 0x00 '?', 0x00 '?'. } } (NCCI=0) (error=0x1101) [2016-02-20 14:55:37.073] NOTICE[21261] chan_capi.c: could not send FACILITY REQUEST! [2016-02-20 14:55:37.073] VERBOSE[21261] chan_capi.c: [2016-02-20 14:55:37.073] -- CAPI controller 0 supports: [DTMF][echo cancellation][supplementary] [2016-02-20 14:55:37.073] ERROR[21261] chan_capi.c: CAPI error sending CAPI_LISTEN_REQ { header { WORD wLen = 0x0000 WORD wApp = 0xffff WORD wCmd = 0x8462 WORD wNum = 0x0002 DWORD dwCid = 0x00000000 } data { DWORD dwInfoMask = 0x0000ffff DWORD dwCipMask1 = 0x1fff03ff DWORD dwCipMask2 = 0x00000000 STRUCT src_telno.ptr = (empty) STRUCT src_subaddr.ptr = (empty) } } (NCCI=0) (error=0x1101) [2016-02-20 14:55:37.073] ERROR[21261] chan_capi.c: Unable to listen on controller=0! [2016-02-20 14:55:37.074] VERBOSE[21261] channel.c: [2016-02-20 14:55:37.074] == Registered channel type 'CAPI' (Common ISDN API 2.0 Driver 2.0.1 5) [2016-02-20 14:55:37.074] VERBOSE[21261] pbx.c: [2016-02-20 14:55:37.074] == Registered application 'capiCommand' [2016-02-20 14:55:37.074] VERBOSE[21261] loader.c: [2016-02-20 14:55:37.074] chan_capi.so => (Common ISDN API 2.0 Driver 2.0.15) Some seconds later: [2016-02-20 14:55:37.125] VERBOSE[21261] asterisk.c: [2016-02-20 14:55:37.125] Asterisk Ready. [2016-02-20 14:55:39.469] VERBOSE[21261] chan_capi.c: [2016-02-20 14:55:39.469] -- CAPI controller 0 supports: [DTMF][echo cancellation][supplementary] [2016-02-20 14:55:40.854] VERBOSE[21261] chan_capi.c: [2016-02-20 14:55:40.854] -- listening on controller=0, cip_mask=0x1fff03ff [2016-02-20 14:55:40.855] WARNING[21261] chan_capi.c: CAPI application was restarted [2016-02-20 14:55:40.855] ERROR[21261] lock.c: chan_capi.c line 2586 (capi_check_wait_get_cmsg): mutex '&p_app->lock' freed more times than we've locked! [2016-02-20 14:55:40.855] ERROR[21261] lock.c: chan_capi.c line 2586 (capi_check_wait_get_cmsg): Error releasing mutex: Operation not permitted Regards Andreas Longwitz From owner-freebsd-isdn@freebsd.org Sat Feb 20 14:55:51 2016 Return-Path: Delivered-To: freebsd-isdn@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D022DAAF5C0 for ; Sat, 20 Feb 2016 14:55:51 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 98CF0B60 for ; Sat, 20 Feb 2016 14:55:51 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id A854C1FE023; Sat, 20 Feb 2016 15:55:46 +0100 (CET) Subject: Re: chan_capi error after update To: Andreas Longwitz References: <56C6E0D4.5060603@incore.de> <56C74704.6060606@selasky.org> <56C83752.6080708@selasky.org> <56C87494.6020605@incore.de> Cc: freebsd-isdn@freebsd.org From: Hans Petter Selasky Message-ID: <56C87F06.1070504@selasky.org> Date: Sat, 20 Feb 2016 15:58:14 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56C87494.6020605@incore.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Feb 2016 14:55:51 -0000 On 02/20/16 15:13, Andreas Longwitz wrote: > Hi, > thanks for investigating in this problem ! > >> I found a minor bug there. I've made v2.0.15 available. Just SVN up and >> install the port. I've also fixed a build issue with later versions of >> asterisk, that it needs the "-fblocks" CFLAG when compiling. >> >> I'm currently using the exact same setup with Asterisk 11.x without any >> such problems. > OK, at the moment I am a little bit late with versions because I use a > consistent portstree 2014Q4 running poudriere on all of my servers. > >> >> --HPS > > After update to chan_capi 2.0.15 (without the -fblocks CFLAG, because > the compiler does not know in V8: cc1: error: unrecognized command line > option "-fblocks") the problem has not gone away. But the order of the > messages is a little bit different now: > Try to update once more. --HPS From owner-freebsd-isdn@freebsd.org Sat Feb 20 15:12:51 2016 Return-Path: Delivered-To: freebsd-isdn@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20D77AAFC62 for ; Sat, 20 Feb 2016 15:12:51 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E10A11138 for ; Sat, 20 Feb 2016 15:12:50 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 0C0EC1FE023; Sat, 20 Feb 2016 16:12:45 +0100 (CET) Subject: Re: chan_capi error after update To: Andreas Longwitz References: <56C6E0D4.5060603@incore.de> <56C74704.6060606@selasky.org> <56C83752.6080708@selasky.org> <56C87494.6020605@incore.de> <56C87F06.1070504@selasky.org> Cc: freebsd-isdn@freebsd.org From: Hans Petter Selasky Message-ID: <56C88301.3060104@selasky.org> Date: Sat, 20 Feb 2016 16:15:13 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56C87F06.1070504@selasky.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Feb 2016 15:12:51 -0000 Hi, Does the output from: capi info make sense? --HPS From owner-freebsd-isdn@freebsd.org Sat Feb 20 16:24:12 2016 Return-Path: Delivered-To: freebsd-isdn@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BF29AAF973 for ; Sat, 20 Feb 2016 16:24:12 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E94DF1181 for ; Sat, 20 Feb 2016 16:24:11 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id AC2A367ADE; Sat, 20 Feb 2016 17:24:09 +0100 (CET) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id bJ8XlmN4JmD0; Sat, 20 Feb 2016 17:24:07 +0100 (CET) Received: from mail.local.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id CD0F3678BF; Sat, 20 Feb 2016 17:24:07 +0100 (CET) Received: from bsdmhs.longwitz (unknown [192.168.99.6]) by mail.local.incore (Postfix) with ESMTP id 6B73A50899; Sat, 20 Feb 2016 17:24:07 +0100 (CET) Message-ID: <56C89326.4030803@incore.de> Date: Sat, 20 Feb 2016 17:24:06 +0100 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Hans Petter Selasky CC: freebsd-isdn@freebsd.org Subject: Re: chan_capi error after update References: <56C6E0D4.5060603@incore.de> <56C74704.6060606@selasky.org> <56C83752.6080708@selasky.org> <56C87494.6020605@incore.de> <56C87F06.1070504@selasky.org> <56C88301.3060104@selasky.org> In-Reply-To: <56C88301.3060104@selasky.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Feb 2016 16:24:12 -0000 Hi, > Try to update once more. Done, update to chan_capi 2.0.16, same result as in 2.0.15, only the two last ERROR messages "lock.c: chan_capi.c line 2586" are gone. Your check for asterisk V11 failed because I have the file ast_version.h in asterisk 1.8 too. > Does the output from: > capi info > make sense? I think yes, this is my capi.conf: [general] language=de nationalprefix=0 internationalprefix=00 rxgain=1.0 txgain=1.0 alaw=yes digit_timeout=1 ton2digit=1 [ISDN] ntmode=no isdnmode=msn incomingmsn=4982871 defaultcid=4982871 controller=0 devices=2 group=1 accountcode= context=isdn-in holdtype=local -> asterisk -r [Feb 20 17:05:41] Asterisk 1.8.32.1, Copyright (C) 1999 - 2013 Digium, Inc. and others. Created by Mark Spencer Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'core show license' for details. ========================================================================= [Feb 20 17:05:41] Connected to Asterisk 1.8.32.1 currently running on loserver (pid = 28258) Verbosity is at least 5 Core debug is at least 3 [2016-02-20 17:05:41.500] -- Remote UNIX connection loserver*CLI> capi info CAPI thread [0x0] { Application ID : 0x00000000 Application uptime : 0x0000003b seconds Backend : capi20 @ localhost Call descriptor statistics: allocation count : 0x00000000 call descriptors free count : 0x00000000 call descriptors in memory count : 0x00000000 call descriptors in use count : 0x00000000 call descriptors record allocation rate : 0x0000 calls/second limit allocation rate : 0x0010 calls/second Currently active calls: channel name, source->destination, call ID, in/out } Config entry 'ISDN' { b_channels_curr : 2 call descriptor(s) free b_channels_max : 2 call descriptor(s) total } Andreas Longwitz From owner-freebsd-isdn@freebsd.org Sat Feb 20 16:33:30 2016 Return-Path: Delivered-To: freebsd-isdn@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A8C9AAFD19 for ; Sat, 20 Feb 2016 16:33:30 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 04E3C15BA for ; Sat, 20 Feb 2016 16:33:29 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 342761FE023; Sat, 20 Feb 2016 17:33:27 +0100 (CET) Subject: Re: chan_capi error after update To: Andreas Longwitz References: <56C6E0D4.5060603@incore.de> <56C74704.6060606@selasky.org> <56C83752.6080708@selasky.org> <56C87494.6020605@incore.de> <56C87F06.1070504@selasky.org> <56C88301.3060104@selasky.org> <56C89326.4030803@incore.de> Cc: freebsd-isdn@freebsd.org From: Hans Petter Selasky Message-ID: <56C895EA.5000404@selasky.org> Date: Sat, 20 Feb 2016 17:35:54 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56C89326.4030803@incore.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Feb 2016 16:33:30 -0000 On 02/20/16 17:24, Andreas Longwitz wrote: > Hi, > >> Try to update once more. > > Done, update to chan_capi 2.0.16, same result as in 2.0.15, only the two > last ERROR messages "lock.c: chan_capi.c line 2586" are gone. Your check > for asterisk V11 failed because I have the file ast_version.h in > asterisk 1.8 too. > > > I think yes, this is my capi.conf: > [general] > language=de > nationalprefix=0 > internationalprefix=00 > rxgain=1.0 > txgain=1.0 > alaw=yes > digit_timeout=1 > ton2digit=1 > > [ISDN] > ntmode=no > isdnmode=msn > incomingmsn=4982871 > defaultcid=4982871 > controller=0 > devices=2 > group=1 > accountcode= > context=isdn-in > holdtype=local > > -> asterisk -r > [Feb 20 17:05:41] Asterisk 1.8.32.1, Copyright (C) 1999 - 2013 Digium, > Inc. and others. > Created by Mark Spencer > Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' > for details. > This is free software, with components licensed under the GNU General Public > License version 2 and other licenses; you are welcome to redistribute it > under > certain conditions. Type 'core show license' for details. > ========================================================================= > [Feb 20 17:05:41] Connected to Asterisk 1.8.32.1 currently running on > loserver (pid = 28258) > Verbosity is at least 5 > Core debug is at least 3 > [2016-02-20 17:05:41.500] -- Remote UNIX connection > loserver*CLI> capi info > CAPI thread [0x0] { > Application ID : 0x00000000 > Application uptime : 0x0000003b seconds > Backend : capi20 @ localhost > > Call descriptor statistics: > allocation count : 0x00000000 call descriptors > free count : 0x00000000 call descriptors > in memory count : 0x00000000 call descriptors > in use count : 0x00000000 call descriptors > record allocation rate : 0x0000 calls/second > limit allocation rate : 0x0010 calls/second > Currently active calls: > channel name, source->destination, call ID, in/out > } > Config entry 'ISDN' { > b_channels_curr : 2 call descriptor(s) free > b_channels_max : 2 call descriptor(s) total > } > Hi, Looks good to me. What happens when you try to dial IN/OUT. Nothing works? And did you try "capitest" to make a CAPI test call? Can you describe a bit more what is not working? --HPS