From owner-freebsd-isdn@FreeBSD.ORG Mon Jan 1 11:08:46 2007 Return-Path: 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 3BD7816A585 for ; Mon, 1 Jan 2007 11:08:46 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 1253913C4AB for ; Mon, 1 Jan 2007 11:08:46 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l01B8jH4048904 for ; Mon, 1 Jan 2007 11:08:45 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l01B8iZl048900 for freebsd-isdn@FreeBSD.org; Mon, 1 Jan 2007 11:08:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Jan 2007 11:08:44 GMT Message-Id: <200701011108.l01B8iZl048900@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-isdn@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jan 2007 11:08:46 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/79117 isdn [iavc] iavc(4) for AVM B1 PCI does not attach 1 problem total. From owner-freebsd-isdn@FreeBSD.ORG Thu Jan 4 17:21:15 2007 Return-Path: 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 407E316A40F for ; Thu, 4 Jan 2007 17:21:15 +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 0741913C469 for ; Thu, 4 Jan 2007 17:21:15 +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 1H2W34-000JM3-W6; Thu, 04 Jan 2007 18:06:39 +0100 Message-ID: <459D3421.6070605@ovb.ch> Date: Thu, 04 Jan 2007 18:06:41 +0100 From: Oliver von Bueren User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-isdn@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ISDN4BSD by HPS - Some more instructions needed X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2007 17:21:15 -0000 Hi to all. I'm running a FreeBSD 6.10-RELEASE-p10 at the moment and have a few small questions with the handling of the ISDN4BSD package from http://www.turbocat.net/~hselasky/isdn4bsd/ by Hans Petter Selasky (short HPS:-)). First of all, it looks like this is the only available option to run passive ISDN cards with Asterisk on FreeBSD.I've got that combination up and running with some issues (call is dropped by i4b/asterisk/??? after about 30 secs). As there have been changes to the source by HPS since 1.6.1 I'm currently installing subversion to update i4b. And now the questions start. - How is i4b by HPS supposed to be updated? Is it correct to do a "make deinstall" of the 1.6.1 and then a "make install" of the new one? - About the same "issue" with updating the base system to get to the next patch release or release of FreeBSD. Is it required to make a deinstall of i4b by HPS followed by a /usr/src>make update / buildworld-Process and then re-installing it all? - And to make this hole thing complete, just another humble opinion about i4b in general. I've been using i4b since a 4.x version of FreeBSD for some small applications. That time it was good and "new". Nowadays the built-in version of i4b has some deficits, namely no CAPI for passive cards. So what do YOU (meaning users of i4b) think about the idea, that the "new" i4b by HPS should be integrated into the base FreeBSD. My opinion is, that this would enhance the functionality of FreeBSD in that area and all the FreeBSD users would benefit. Oliver From owner-freebsd-isdn@FreeBSD.ORG Thu Jan 4 23:04:02 2007 Return-Path: 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 DE0EC16A407 for ; Thu, 4 Jan 2007 23:04:02 +0000 (UTC) (envelope-from mc467741@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id 5904913C469 for ; Thu, 4 Jan 2007 23:03:58 +0000 (UTC) (envelope-from mc467741@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [84.188.238.66] (account mc467741@c2i.net) by mailbe05.swip.net (CommuniGate Pro WebUser 5.0.12) with HTTP id 51146792; Thu, 04 Jan 2007 23:03:51 +0100 From: "Hans Petter" To: Oliver von Bueren , freebsd-isdn@freebsd.org X-Mailer: CommuniGate Pro WebUser v5.0.12 Date: Thu, 04 Jan 2007 23:03:51 +0100 Message-ID: In-Reply-To: <459D3421.6070605@ovb.ch> References: <459D3421.6070605@ovb.ch> X-Priority: 3 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: ISDN4BSD by HPS - Some more instructions needed X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2007 23:04:02 -0000 Hi Oliver, On Thu, 04 Jan 2007 18:06:41 +0100 Oliver von Bueren wrote: > Hi to all. > > I'm running a FreeBSD 6.10-RELEASE-p10 at the moment and >have a few small questions with the handling of the >ISDN4BSD package from >http://www.turbocat.net/~hselasky/isdn4bsd/ by Hans >Petter Selasky (short HPS:-)). > >First of all, it looks like this is the only available >option to run passive ISDN cards with Asterisk on >FreeBSD.I've got that combination up and running with >some issues (call is dropped by i4b/asterisk/??? after >about 30 secs). As there have been changes to the source >by HPS since 1.6.1 I'm currently installing subversion to >update i4b. And now the questions start. > If you get calls dropped, try running the tool "isdndecode" given the paramete r "-u 0" where "0" is the controller number you wish to log. Then record the standard output and put it somewhere or mail it to me, and I will have a look. > - How is i4b by HPS supposed to be updated? Is it >correct to do a "make deinstall" of the 1.6.1 and then a >"make install" of the new one? The correct is to "make deinstall" the old one and then "make install" the new one. > - About the same "issue" with updating the base system >to get to the next patch release or release of FreeBSD. >Is it required to make a deinstall of i4b by HPS followed >by a /usr/src>make update / buildworld-Process and then >re-installing it all? It might be a good idea to CVSUP your FreeBSD kernel and userland sources before you install the I4B driver. Depending on how much has changed in the kernel sources you should consider to "make a new world", to reduce problems with incompatible kernel ioctls. > - A nd to make this hole thing complete, just another >humble opinion about i4b in general. I've been using i4b >since a 4.x version of FreeBSD for some small >applications. That time it was good and "new". Nowadays >the built-in version of i4b has some deficits, namely no >CAPI for passive cards. So what do YOU (meaning users of >i4b) think about the idea, that the "new" i4b by HPS >should be integrated into the base FreeBSD. My opinion >is, that this would enhance the functionality of FreeBSD >in that area and all the FreeBSD users would benefit. > --HPS From owner-freebsd-isdn@FreeBSD.ORG Sat Jan 6 16:17:25 2007 Return-Path: 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 6FB8B16A40F for ; Sat, 6 Jan 2007 16:17:25 +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 171AF13C45A for ; Sat, 6 Jan 2007 16:17:24 +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 1H3EEU-000BHE-OG; Sat, 06 Jan 2007 17:17:22 +0100 Message-ID: <459FCB94.9080600@ovb.ch> Date: Sat, 06 Jan 2007 17:17:24 +0100 From: Oliver von Bueren User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-isdn@freebsd.org References: <459D3421.6070605@ovb.ch> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ISDN4BSD by HPS - Some more instructions needed X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jan 2007 16:17:25 -0000 Hi Hans Petter That worked great, after getting the newest version by svn and doing a make help I've seen that you point that out there as well. Thanks! For others who perhaps have the same issue, here is the short form of what I did: 0. svn ... svn://svn.turbocat.net/i4b # Get the newest version of i4b by HPS (into a new directory) 1. portupgrade -R asterisk # Update asterisk for a newer version if needed 2. make deinstall # Uninstall (old version of) i4b by HPS with: 3. /usr/src> make update # Update FreeBSD, in my case to 6.1-RELEASE-p11 4. make buildworld / .... # FreeBSD update process as usual, but without a reboot yet! 5. i4b/trunk/i4b/FreeBSD.i4b> make S=../src package 6. i4b/trunk/i4b/FreeBSD.i4b> make install 7. i4b/trunk/chan_capi> gmake all install 8. /usr/src> make buildkernel KERNCONF=.... # build the kernel with i4b configured 9. /usr/src> make installkernel KERNCONF=... # install kernel 10. reboot 11. /usr/src> make installworld This is the long run with rebuilding world. If no FreeBSD update is done, but only i4b, the following should do: 0, 2, 5, 6, 7, 8, 9, 10 For anyone not familiar with buildworld please consult the FreeBSD manual for a more detailed version of it. And for the compile options to reduce time for re-building the kernel after just a i4b update, see the help files by HPS. Oliver Hans Petter wrote: > Hi Oliver, > > On Thu, 04 Jan 2007 18:06:41 +0100 > Oliver von Bueren wrote: > > Hi to all. > > > > I'm running a FreeBSD 6.10-RELEASE-p10 at the moment and > >have a few small questions with the handling of the > >ISDN4BSD package from > >http://www.turbocat.net/~hselasky/isdn4bsd/ by Hans > >Petter Selasky (short HPS:-)). > > > >First of all, it looks like this is the only available > >option to run passive ISDN cards with Asterisk on > >FreeBSD.I've got that combination up and running with > >some issues (call is dropped by i4b/asterisk/??? after > >about 30 secs). As there have been changes to the source > >by HPS since 1.6.1 I'm currently installing subversion to > >update i4b. And now the questions start. > > > > If you get calls dropped, try running the tool "isdndecode" given the > parameter "-u 0" where "0" is the controller number you wish to log. > Then record the standard output and put it somewhere or mail it to me, > and I will have a look. > > > - How is i4b by HPS supposed to be updated? Is it > >correct to do a "make deinstall" of the 1.6.1 and then a > >"make install" of the new one? > > The correct is to "make deinstall" the old one and then "make install" > the new one. > > > - About the same "issue" with updating the base system > >to get to the next patch release or release of FreeBSD. > >Is it required to make a deinstall of i4b by HPS followed > >by a /usr/src>make update / buildworld-Process and then > >re-installing it all? > > It might be a good idea to CVSUP your FreeBSD kernel and userland > sources before you install the I4B driver. Depending on how much has > changed in the kernel sources you should consider to "make a new > world", to reduce problems with incompatible kernel ioctls. > > > - And to make this hole thing complete, just another > >humble opinion about i4b in general. I've been using i4b > >since a 4.x version of FreeBSD for some small > >applications. That time it was good and "new". Nowadays > >the built-in version of i4b has some deficits, namely no > >CAPI for passive cards. So what do YOU (meaning users of > >i4b) think about the idea, that the "new" i4b by HPS > >should be integrated into the base FreeBSD. My opinion > >is, that this would enhance the functionality of FreeBSD > >in that area and all the FreeBSD users would benefit. > > > > --HPS From owner-freebsd-isdn@FreeBSD.ORG Sat Jan 6 16:23:57 2007 Return-Path: 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 1CF7D16A40F for ; Sat, 6 Jan 2007 16:23:57 +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 D8F1C13C44C for ; Sat, 6 Jan 2007 16:23:56 +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 1H3EKq-000BUS-1F; Sat, 06 Jan 2007 17:23:56 +0100 Message-ID: <459FCD1E.9080303@ovb.ch> Date: Sat, 06 Jan 2007 17:23:58 +0100 From: Oliver von Bueren User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-isdn@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ISDN4BSD - Dropped Calls X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jan 2007 16:23:57 -0000 Hi Hans Petter As said in the last post about the update procedure, here are my traces concerning the disconnect after some 13 seconds. Calling from the ISDN side to Asterisk works fine, voice is played but then of a sudden, it stops/disconnects. I tried to get into the source of i4b but without much luck, I'm not used to driver code on FreeBSD. Following my findings after going through the traces including a link to the traces itself. Any ideas? Oliver ==== Additional information to the trace Software Versions FreeBSD 6.1-RELEASE-p11 (after a complete build/install world/kernel) (cvsup dated 20070104 around 18:00 GMT, RELENG_6_1) From Ports (cvsup dated 20070104 around 18:00 GMT) Asterisk 1.2.13, Copyright (C) 1999 - 2006 Digium, Inc. and others. ISDN4BSD (incl. chan_capi) via svn, 20070104 around 19:00 GMT) ==== The full trace files are on http://www.ovb.ch/i4b/isdn-trace-20070105.tar.gz ==== It's a base installation of Asterisk and i4b/chan_capi Connected to a PABX. All numbers starting with 84* terminate on the S0 the FreeBSD is connected to. Fresh startup of asterisk and isdntrace: asterisk -cdfgvvvvvvT // ISDN Debuging is enabled in capi.conf isdndecode -u 0 -i -x -r Extension 811 calls 840. Up to and including frame 117 the greeting voice from the default installation can be heard without problem. Then the sound stops. Frame 118-119 come in at the time the voice stops. Frame 120-121 shortly afterwards Frame 122- Hangup on the still connected (?) phone Stop isdntrace and asterisk I've done some analysing of this trace. BTW: I'm doing software development of a Dialogic PRI card (E1 in QSig mode), so I'm somewhat used to this kind of traces. NT is the PABX and TE is Asterisk/chan_capi/i4b. So lets see what happens. - F93 is a SETUP message for Call 0x35 => OK - F94/F95 is a TEI req and resp => OK - F97/F98 is quite strange, here TE makes two STATUS_ENQUIRY for call 0x7F. This is not a call ID we've had so far and looks like a MAX-Value to me. - F101 these ENQs are answered by NT with a RELEASE/invalid call ref id. Which to me looks quite correct. - F103 is the SETUP_ACK by TE => OK - F104 a PROCEEDINg by TE => OK - F105 TE tries to clean-up the Call 0x7F and sends a REL_COMPLETE, also with cause invalid call ref. id - F106: Release to the second STAT_ENQ by NT (see F101) - F109: see F105 - F111: We connect the call 0x35 => OK - F113: NT sends CON_ACK => OK - F116: TE makes a STAT_ENQ for Call 0x35 - F118: TE sends a REL_COMPLETE for Call 0x35 => ?? - F122: NT answers with DISCoNNECT My questions in this scenario are: Why are the STATUS_ENQs sent two times for Call 0x7f, which obvoiusly are not valid ones? My guess: The two available ISDN channels are initialised with call 0x7F and now cause some confusion. Why does TE send a REL_COM with F118? Has this still to do with the 0x7F-Call and some mixup with the channels. It doesn't look like a clean hangup by TE. === As you can see from the options of Asterisk, I've done a trace there as well. In the Asterisk-Trace the TEI assignment and STAT_ENQs for the 0x7F-Calls is not visible, it looks like that is not initiated by chan_capi. For the CAPI stuff in the trace, it looks quite good up to the point where a CAPI_DISCONNECT_B3_IND pops up. But I can't tell where that one is comming from. From the point on where the phone drops the call as well, it takes still some seconds till the PBX cleans up the call completely. If you do that several times, you can end up having both channels "blocked" without actually having a work connection. A call will fail with a busy then. From owner-freebsd-isdn@FreeBSD.ORG Sat Jan 6 18:09:15 2007 Return-Path: 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 CE94E16A40F for ; Sat, 6 Jan 2007 18:09:15 +0000 (UTC) (envelope-from mc467741@c2i.net) Received: from swip.net (mailfe09.swip.net [212.247.155.1]) by mx1.freebsd.org (Postfix) with ESMTP id CE1B113C44B for ; Sat, 6 Jan 2007 18:09:14 +0000 (UTC) (envelope-from mc467741@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [84.188.236.174] (account mc467741@c2i.net) by mailbe05.swip.net (CommuniGate Pro WebUser 5.0.12) with HTTP id 51294860; Sat, 06 Jan 2007 18:09:02 +0100 From: "Hans Petter" To: Oliver von Bueren , freebsd-isdn@freebsd.org X-Mailer: CommuniGate Pro WebUser v5.0.12 Date: Sat, 06 Jan 2007 18:09:02 +0100 Message-ID: In-Reply-To: <459FCD1E.9080303@ovb.ch> References: <459FCD1E.9080303@ovb.ch> X-Priority: 3 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jan 2007 18:09:16 -0000 Hi Oliver, On Sat, 06 Jan 2007 17:23:58 +0100 Oliver von Bueren wrote: > Hi Hans Petter > > As said in the last post about the update procedure, >here are my traces concerning the disconnect after some >13 seconds. Calling from the ISDN side to Asterisk works >fine, voice is played but then of a sudden, it >stops/disconnects. > > I tried to get into the source of i4b but without much >luck, I'm not used to driver code on FreeBSD. > >Following my findings after going through the traces >including a link to the traces itself. Any ideas? > > Oliver > > ==== > Additional information to the trace > > Software Versions >FreeBSD 6.1-RELEASE-p11 (after a complete build/install >world/kernel) > (cvsup dated 20070104 around 18:00 GMT, RELENG_6_1) > > From Ports (cvsup dated 20070104 around 18:00 GMT) > Asterisk 1.2.13, Copyright (C) 1999 - 2006 Digium, Inc. >and others. > > ISDN4BSD (incl. chan_capi) via svn, 20070104 around >19:00 GMT) > > ==== > The full trace files are on > http://www.ovb.ch/i4b/isdn-trace-20070105.tar.gz > ==== > > It's a base installation of Asterisk and i4b/chan_capi > > Connected to a PABX. > All numbers starting with 84* terminate on the S0 the >FreeBSD is connected to. > >Fresh startup of asterisk and isdntrace: > asterisk -cdfgvvvvvvT // ISDN Debuging is enabled in >capi.conf > isdndecode -u 0 -i -x -r > > Extension 811 calls 840. > > Up to and including frame 117 the greeting voice from >the default installation > can be heard without problem. Then the sound stops. >Frame 118-119 come in at the time the voice stops. >Frame 120-121 shortly afterwards >Frame 122- Hangup on the still connected (?) phone > > Stop isdntrace and asterisk > > I've done some analysing of this trace. BTW: I'm doing >software development > of a Dialogic PRI card (E1 in QSig mode), so I'm >somewhat used to this kind > of traces. > NT is the PABX and TE is Asterisk/chan_capi/i4b. > > So lets see what happens. > - F93 is a SETUP message for Call 0x35 => OK > - F94/F95 is a TEI req and resp => OK > - F97/F98 is quite strange, here TE makes two >STATUS_ENQUIRY for call 0x7F. These are dummy messages, which are part of the procedure to bring up the layer 2 "TCP" connection. The idea was to send a zero length I-frame, but many PBX's simply lack a check for zero length I-frames and will continue to process the frame as if data was present leading to crashes i n most cases. To avoid this, I send four extra bytes, which makes up the STATUS_ENQUIRY message. > This is not a call ID we've had so far and looks like a >MAX-Value to me. The call ID 0x7F is never used for outgoing calls from the I4B. > - F101 these ENQs are answered by NT with a >RELEASE/invalid call ref id. It indicates that the PBX creates a new call at the moment it receives a new Call-reference messages. Really it should do nothing when the call reference is invalid, or maybe send a RELEASE_COMPLETE. But not RELEASE. > Which to me looks quite correct. > - F103 is the SETUP_ACK by TE => OK > - F104 a PROCEEDINg by TE => OK > - F105 TE tries to clean-up the Call 0x7F and sends a >REL_COMPLETE, also > with cause invalid call ref. id If you don't send a message back in reply to the RELEASE message, the NT-side will most likely send a RESTART message or just hang up all c alls, from my experience. > - F106: Release to the second STAT_ENQ by NT (see F101) > - F109: see F105 > - F111: We connect the call 0x35 => OK > - F113: NT sends CON_ACK => OK > > - F116: TE makes a STAT_ENQ for Call 0x35 > > - F118: TE sends a REL_COMPLETE for Call 0x35 => ?? I4B will hangup the call if the NT-side does not respond to STATUS_ENQUIRY, after 8 to 16 seconds. This is just a safety mechanism. The DSS1 specification says that implementing STATUS_ENQUIRY response is mandatory. > > - F122: NT answers with DISCoNNECT > > My questions in this scenario are: Why are the >STATUS_ENQs sent two times for > Call 0x7f, which obvoiusly are not valid ones? My guess: >The two available > ISDN channels are initialised with call 0x7F and now >cause some confusion. It is just how I4B starts up the D-channel. It sends two I-frames and waits until it gets a reply before it sends more frames. This avoids races with SABME/UA. > Why does TE send a REL_COM with F118? Has this still to >do with the 0x7F-Call > and some mixup with the channels. It doesn't look like a >clean hangup by TE. Because else the NT-side will most likely do a reset on all active calls. The reason I4B hangs up is because the NT-side does not reply to the last STATUS_ENQUIRY message for call reference 0x35 in your log. --HPS From owner-freebsd-isdn@FreeBSD.ORG Sat Jan 6 21:20:51 2007 Return-Path: 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 9BA4216A403 for ; Sat, 6 Jan 2007 21:20:51 +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 6665713C467 for ; Sat, 6 Jan 2007 21:20:51 +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 1H3IyA-000LID-Fk; Sat, 06 Jan 2007 22:20:50 +0100 Message-ID: <45A012B3.9050809@ovb.ch> Date: Sat, 06 Jan 2007 22:20:51 +0100 From: Oliver von Bueren User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-isdn@freebsd.org References: <459FCD1E.9080303@ovb.ch> In-Reply-To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jan 2007 21:20:51 -0000 Hello Hans Petter Thanks for pointing me to the reason for the STATUS_ENQUIRY messages with an invalid call reference. I've checked the behaviour after changing the code in dss1_l2_get_mbuf to not append any data but send the packet on without the STATUS_ENQUIRY attached. This did not change the overall result, except of course that the releasing of the "fake" call does not happen any more. Kind of a prove that this method used here does not confuse the PBX. As you wrote, a STATUS_ENQUIRY (I'm now talking about the one for the real call) needs to be answered by the PBX, which according to the trace, it does not. No idea why this is, I'll try to get a trace form the PBX. The strange thing is, that a lot of other applications connected to that PBX/port run without problem, even a FreeBSD 4.3 with the then-current i4b and some voice response system. Amongst the other working things are hardware phones/modems and even an active Card (Eicon Diva Pro 2.0) running under windows with the sort-of cygwin-port of Asterisk (from http://www.asteriskwin32.com/) runs without any problems. But as you can guess, I'd like to get away from that stone-age Asterisk version and change to my FreeBSD server. If I find anything, I'll keep you posted. If you've any ideas on how to fix my problem, drop me a note. Thanks! Oliver Hans Petter wrote: > > - F97/F98 is quite strange, here TE makes two > >STATUS_ENQUIRY for call 0x7F. > > These are dummy messages, which are part of the procedure to bring up > the layer 2 "TCP" connection. The idea was to send a zero length > I-frame, but many PBX's simply lack a check for zero length I-frames > and will continue to process the frame as if data was present leading > to crashes in most cases. To avoid this, I send four extra bytes, > which makes up the STATUS_ENQUIRY message. > [...] > > - F116: TE makes a STAT_ENQ for Call 0x35 > > > > - F118: TE sends a REL_COMPLETE for Call 0x35 => ?? > > I4B will hangup the call if the NT-side does not respond to > STATUS_ENQUIRY, after 8 to 16 seconds. This is just a safety > mechanism. The DSS1 specification says that implementing > STATUS_ENQUIRY response is mandatory. From owner-freebsd-isdn@FreeBSD.ORG Sat Jan 6 21:56:56 2007 Return-Path: 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 28F7E16A40F for ; Sat, 6 Jan 2007 21:56:56 +0000 (UTC) (envelope-from mc467741@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id 4DF1F13C455 for ; Sat, 6 Jan 2007 21:56:55 +0000 (UTC) (envelope-from mc467741@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [84.188.236.174] (account mc467741@c2i.net) by mailbe03.swip.net (CommuniGate Pro WebUser 5.0.12) with HTTP id 54124816; Sat, 06 Jan 2007 22:56:53 +0100 From: "Hans Petter" To: Oliver von Bueren , freebsd-isdn@freebsd.org X-Mailer: CommuniGate Pro WebUser v5.0.12 Date: Sat, 06 Jan 2007 22:56:53 +0100 Message-ID: In-Reply-To: <45A012B3.9050809@ovb.ch> References: <459FCD1E.9080303@ovb.ch> <45A012B3.9050809@ovb.ch> X-Priority: 3 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jan 2007 21:56:56 -0000 Hi Oliver, On Sat, 06 Jan 2007 22:20:51 +0100 Oliver von Bueren wrote: > Hello Hans Petter > > Thanks for pointing me to the reason for the >STATUS_ENQUIRY messages with an invalid call reference. >I've checked the behaviour after changing the code in > dss1_l2_get_mbuf to not append any data but send the >packet on without the STATUS_ENQUIRY attached. This did >not change the overall result, except of course that the >releasing of the "fake" call does not happen any more. >Kind of a prove that this method used here does not >confuse the PBX. > > As you wrote, a STATUS_ENQUIRY (I'm now talking about >the one for the real call) needs to be answered by the >PBX, which according to the trace, it does not. No idea >why this is, I'll try to get a trace form the PBX.< br>> > The strange thing is, that a lot of other applications >connected to that PBX/port run without problem, even a >FreeBSD 4.3 with the then-current i4b and some voice >response system. Amongst the other working things are >hardware phones/modems and even an active Card (Eicon >Diva Pro 2.0) running under windows with the sort-of >cygwin-port of Asterisk (from >http://www.asteriskwin32.com/) runs without any problems. >But as you can guess, I'd like to get away from that >stone-age Asterisk version and change to my FreeBSD >server. 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. In "cd_set_state()" you have the following code: cd->state = newstate; /* re-start timeout; * the timeout is increased when L1 is not activated * the timeout is always running while the CD is allocated */ __callout_reset(&cd->set_state_callout, (L3_STATES_TIMEOUT_DELAY[newstate]*hz) + (sc->L1_activity ? 0 : L1_ACTIVATION_TIME), & nbsp; (void *)(void *)&cd_set_state_timeout, cd); if(send_status_enquiry) { /* need to check status regularly */ dss1_l3_tx_status_enquiry(cd); } You can try putting: if (send_status_enquiry) { newstate--; } Before: cd->state = newstate; That will prevent the status expiry timer from elapsing. Yours --HPS