From bugmaster at FreeBSD.org Mon Jun 2 11:06:55 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 2 11:07:07 2008 Subject: Current problem reports assigned to freebsd-isdn@FreeBSD.org Message-ID: <200806021106.m52B6sHk093199@freefall.freebsd.org> 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 bz at FreeBSD.org Tue Jun 3 19:00:06 2008 From: bz at FreeBSD.org (bz@FreeBSD.org) Date: Tue Jun 3 19:00:08 2008 Subject: kern/79117: [iavc] iavc(4) for AVM B1 PCI does not attach Message-ID: <200806031900.m53J05FV089153@freefall.freebsd.org> Synopsis: [iavc] iavc(4) for AVM B1 PCI does not attach State-Changed-From-To: suspended->feedback State-Changed-By: bz State-Changed-When: Tue Jun 3 18:59:39 UTC 2008 State-Changed-Why: See if we'll get feedback or if we can close this. Responsible-Changed-From-To: freebsd-isdn->bz Responsible-Changed-By: bz Responsible-Changed-When: Tue Jun 3 18:59:39 UTC 2008 Responsible-Changed-Why: See if we'll get feedback or if we can close this. http://www.freebsd.org/cgi/query-pr.cgi?pr=79117 From outi at bytephobia.de Wed Jun 4 13:45:22 2008 From: outi at bytephobia.de (Patrick Hurrelmann) Date: Wed Jun 4 13:45:30 2008 Subject: FreeBSD and libcapi20 with Remote-Capi Message-ID: <1212586291.6474.17.camel@ip6-localhost> Hi Hans-Petter, first I'd like to thank you for your awesome work and effort to bring FreeBSD's usb and isdn support forward and to keep it alive. Thank you very much! Now as it seems that updated usb-support is quite near I'm facing new problems that i cannot currently handle. As I probably don't know how to describe it best, I will simply start with the aim that I'd like to achieve. Connect to several Bintec ISDN-routers via Remote-Capi. A Java-based software is installed locally on FreeBSD 7.0 boxes and it needs to connect to those Bintec-Routers by Remote-Capi. Now there's a JNI-wrapper for Java that calls libcapi20.so (called jcapi, see jcapi.sf.net). So what I'm basically missing is a libcapi20 for FreeBSD that is either Remote-Capi capable or your valuable help or suggestions as a FreeBSD isdn and kernel hacker. Additionally there is also an old library provided by Bintec itself with Remote-Capi support, but i fail to understand how to plug it in into the whole system (and fail to change the Makefile to build shared libs instead of static ones). This old library is available at ftp://ftp.bintec.de/pub/libcapi/capi_1.7.5.tar.gz I'm also forwarding this to freebsd-isdn@ as maybe others have already faced this problem, although i could not find any references across the net about this. Help or any hints are really appreciated, as I need to handle this and this block communication via ISDN. If I can't solve/work around this issue I will have to move the whole application from FreeBSD to Linux :/ Best regards from Germany Patrick Hurrelmann -- ?==================== Patrick Hurrelmann Mannheim, Germany outi@bytephobia.de www.bytephobia.de From hselasky at c2i.net Wed Jun 4 16:13:00 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Jun 4 16:13:07 2008 Subject: FreeBSD and libcapi20 with Remote-Capi In-Reply-To: <1212586291.6474.17.camel@ip6-localhost> References: <1212586291.6474.17.camel@ip6-localhost> Message-ID: <200806041714.27614.hselasky@c2i.net> Hi Patrick, Are these Bintec ISDN-routers CAPI clients or are they CAPI servers? If you want we can discuss on phone/AIM/ICQ/IRC/MSN etc ... --HPS On Wednesday 04 June 2008, Patrick Hurrelmann wrote: > Hi Hans-Petter, > > first I'd like to thank you for your awesome work and effort to bring > FreeBSD's usb and isdn support forward and to keep it alive. Thank you > very much! > > Now as it seems that updated usb-support is quite near I'm facing new > problems that i cannot currently handle. As I probably don't know how to > describe it best, I will simply start with the aim that I'd like to > achieve. > > Connect to several Bintec ISDN-routers via Remote-Capi. A Java-based > software is installed locally on FreeBSD 7.0 boxes and it needs to > connect to those Bintec-Routers by Remote-Capi. Now there's a > JNI-wrapper for Java that calls libcapi20.so (called jcapi, see > jcapi.sf.net). > > So what I'm basically missing is a libcapi20 for FreeBSD that is either > Remote-Capi capable or your valuable help or suggestions as a FreeBSD > isdn and kernel hacker. Additionally there is also an old library > provided by Bintec itself with Remote-Capi support, but i fail to > understand how to plug it in into the whole system (and fail to change > the Makefile to build shared libs instead of static ones). This old > library is available at > ftp://ftp.bintec.de/pub/libcapi/capi_1.7.5.tar.gz > > I'm also forwarding this to freebsd-isdn@ as maybe others have already > faced this problem, although i could not find any references across the > net about this. > > Help or any hints are really appreciated, as I need to handle this and > this block communication via ISDN. If I can't solve/work around this > issue I will have to move the whole application from FreeBSD to Linux :/ > > > Best regards from Germany > > Patrick Hurrelmann From info at denisio.net Tue Jun 10 15:12:06 2008 From: info at denisio.net (Denis Beltramo) Date: Tue Jun 10 15:12:11 2008 Subject: Problem with mutilink Message-ID: <27f0c3e40806100747p54e156ffo6f8103ea12542c94@mail.gmail.com> Hello, I have a problem with multilink with isdn4bsd and ppp... simply don't go up second channel. My configuration are: isdnd.rc: system acctall= on acctfile = /var/log/isdnd.acct isdntime = on monitor-allowed = no entry name = userppp0 usrdevicename = rbch usrdeviceunit = 0 isdncontroller = 63 isdnchannel = -1 local-phone-incoming = 1234567 remote-phone-incoming = * local-phone-dialout = 1234567 remote-phone-dialout = 07012232343 # ppp(8) will override this remdial-handling = first dialin-reaction = ignore dialout-type = normal b1protocol = hdlc idletime-incoming = 0 # Should be larger than ppps timeout idletime-outgoing = 0 # Should be larger than ppps timeout ratetype = 0 unitlength = 90 unitlengthsrc = rate dialretries = -1 dialrandincr = on recoverytime = 1 # Should be smaller than ppps redial usedown = off downtries = 2 downtime = 30 ppp.conf default: set cd 180 set device /dev/i4brbch0 set dial set hangup set login set proctitle ppp-isdn set speed sync nat enable yes provider: set phone "07012232343" # Nummer des Internetproviders set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR enable dns set authname pippo set authkey pluto set mrru 1500 set mru 1504 clone 1,2 link deflink rm link * set mode auto link You have suggestion? -- Denis Beltramo From hselasky at c2i.net Wed Jun 11 10:51:13 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Jun 11 10:51:18 2008 Subject: Problem with mutilink In-Reply-To: <27f0c3e40806100747p54e156ffo6f8103ea12542c94@mail.gmail.com> References: <27f0c3e40806100747p54e156ffo6f8103ea12542c94@mail.gmail.com> Message-ID: <200806111152.33301.hselasky@c2i.net> On Tuesday 10 June 2008, Denis Beltramo wrote: > Hello, > > I have a problem with multilink with isdn4bsd and ppp... simply don't go up > second channel. > My configuration are: > Hi, You need to setup two userppp0 entries in isdnd.rc. And then you need to add some more entries to ppp.conf . I think it should be documented on the internet somewhere. I don't have these entries right here and now. --HPS > isdnd.rc: > > system > acctall= on > acctfile = /var/log/isdnd.acct > isdntime = on > monitor-allowed = no > entry > name = userppp0 > usrdevicename = rbch > usrdeviceunit = 0 > isdncontroller = 63 > isdnchannel = -1 > local-phone-incoming = 1234567 > remote-phone-incoming = * > local-phone-dialout = 1234567 > remote-phone-dialout = 07012232343 # ppp(8) will override this > remdial-handling = first > dialin-reaction = ignore > dialout-type = normal > b1protocol = hdlc > idletime-incoming = 0 # Should be larger than ppps > timeout idletime-outgoing = 0 # Should be larger than > ppps timeout ratetype = 0 > unitlength = 90 > unitlengthsrc = rate > dialretries = -1 > dialrandincr = on > recoverytime = 1 # Should be smaller than ppps > redial usedown = off > downtries = 2 > downtime = 30 > > ppp.conf > > default: > set cd 180 > set device /dev/i4brbch0 > set dial > set hangup > set login > set proctitle ppp-isdn > set speed sync > nat enable yes > > provider: > set phone "07012232343" # Nummer des Internetproviders > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > add default HISADDR > enable dns > set authname pippo > set authkey pluto > set mrru 1500 > set mru 1504 > clone 1,2 > link deflink rm > link * set mode auto > link > > You have suggestion? From tingox at gmail.com Sun Jun 22 16:43:38 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Sun Jun 22 16:43:40 2008 Subject: isdntrace - getting old output format back? Message-ID: Hello, The output format of isdntrace have cahnged in recent versions of ISND4BSD[1]. Is thare an easy way to get the old output format back? Probably not, but I thought it best to check first. I know about the isdndecode command, but it also has the new output format. I am using callid[2] to do call logging of my phone line, using a machine running FreeBSD 5.4-prerelease, and a HFC-based ISDN card (thus the need for ISDN4BSD). The machine[3] used is an old Compaq DeskPro with a PII cpu @ 266 MHz, 96 MB RAM and a 8 GB disk.callid relies on the old output format of isdntrace to detect called and calling numbers. Since FreeBSD 5.4 is unsupported, started to upgrade the machine. First I upgraded to latest 5.5-stable, which required a new version of ISDN4BSD, I found that v 1.5.10 worked. But the I hit the new output format of isdntrace (and isdndecode), which makes callid non-functional. References: 1) ISND4BSD - http://www.turbocat.net/~hselasky/isdn4bsd/ 2) callid - http://www.freshports.org/misc/callid/ 3) machine used - http://tingox.googlepages.com/dp686t3 -- Regards, Torfinn Ingolfsen From hselasky at c2i.net Sun Jun 22 21:51:28 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Jun 22 21:51:33 2008 Subject: isdntrace - getting old output format back? In-Reply-To: References: Message-ID: <200806222352.55786.hselasky@c2i.net> On Sunday 22 June 2008, Torfinn Ingolfsen wrote: > Hello, > > The output format of isdntrace have cahnged in recent versions of > ISND4BSD[1]. Is thare an easy way to get the old output format back? > Probably not, but I thought it best to check first. > I know about the isdndecode command, but it also has the new output format. > > I am using callid[2] to do call logging of my phone line, using a > machine running FreeBSD 5.4-prerelease, and a HFC-based ISDN card > (thus the need for ISDN4BSD). > The machine[3] used is an old Compaq DeskPro with a PII cpu @ 266 MHz, > 96 MB RAM and a 8 GB disk.callid relies on the old output format of > isdntrace to detect called and calling numbers. > Since FreeBSD 5.4 is unsupported, started to upgrade the machine. > First I upgraded to latest 5.5-stable, which required a new version of > ISDN4BSD, I found that v 1.5.10 worked. But the I hit the new output > format of isdntrace (and isdndecode), which makes callid > non-functional. > > References: > 1) ISND4BSD - http://www.turbocat.net/~hselasky/isdn4bsd/ > 2) callid - http://www.freshports.org/misc/callid/ > 3) machine used - http://tingox.googlepages.com/dp686t3 Have you tried isdndecode ? --HPS From hselasky at c2i.net Sun Jun 22 22:00:03 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Jun 22 22:00:06 2008 Subject: isdntrace - getting old output format back? In-Reply-To: <200806222352.55786.hselasky@c2i.net> References: <200806222352.55786.hselasky@c2i.net> Message-ID: <200806230001.37104.hselasky@c2i.net> Hi again, I think this issue has been fixed, but you need to use to stuff from SVN. The 1.5.10 package is too old! And you need to use FreeBSD 6+ . --HPS > > > > References: > > 1) ISND4BSD - http://www.turbocat.net/~hselasky/isdn4bsd/ > > 2) callid - http://www.freshports.org/misc/callid/ > > 3) machine used - http://tingox.googlepages.com/dp686t3 > From tingox at gmail.com Mon Jun 23 15:40:18 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Mon Jun 23 15:40:31 2008 Subject: isdntrace - getting old output format back? In-Reply-To: <200806222352.55786.hselasky@c2i.net> References: <200806222352.55786.hselasky@c2i.net> Message-ID: Hi, > Have you tried isdndecode ? Yes, I have. However, I couldn't find a way to make it produce the old output fromat. -- Regards, Torfinn Ingolfsen From tingox at gmail.com Mon Jun 23 15:41:56 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Mon Jun 23 15:41:59 2008 Subject: isdntrace - getting old output format back? In-Reply-To: <200806230001.37104.hselasky@c2i.net> References: <200806222352.55786.hselasky@c2i.net> <200806230001.37104.hselasky@c2i.net> Message-ID: Hello again, On Mon, Jun 23, 2008 at 12:01 AM, Hans Petter Selasky wrote: > Hi again, > > I think this issue has been fixed, but you need to use to stuff from SVN. The > 1.5.10 package is too old! And you need to use FreeBSD 6+ . Ok, I'll try to upgrade the old machine once more. This time from 5.5 -> 6.3. -- Regards, Torfinn Ingolfsen From tingox at gmail.com Thu Jun 26 17:25:56 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Thu Jun 26 17:25:59 2008 Subject: isdntrace - getting old output format back? In-Reply-To: <200806230001.37104.hselasky@c2i.net> References: <200806222352.55786.hselasky@c2i.net> <200806230001.37104.hselasky@c2i.net> Message-ID: Hi, On Mon, Jun 23, 2008 at 12:01 AM, Hans Petter Selasky wrote: > Hi again, > > I think this issue has been fixed, but you need to use to stuff from SVN. The > 1.5.10 package is too old! And you need to use FreeBSD 6+ . Ok, I finally got the old machine[1] upgraded to FreeBSD 6.3-stable, and installed the latest ISDN4BSD from svn (revision 755). Both isdntrace and isdndecode still uses the new output format (text-formatted hexdump with annotations). I tried all switches / options on isdndecode but couldn't get it to output the old text format. Is there something I have overlooked? To be precise, the call-logd script expects strings like the following (it greps for them): called party number: 99999999 calling party number: 99999999 where '99999999' will be the actual number calling / called. Is it possible to get either isdntrace or isdndecode to output that format? References: 1) machine used: http://tingox.googlepages.com/dp686t3_freebsd -- Regards, Torfinn Ingolfsen, Norway From hselasky at c2i.net Thu Jun 26 20:18:06 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Jun 26 20:18:12 2008 Subject: isdntrace - getting old output format back? In-Reply-To: References: <200806230001.37104.hselasky@c2i.net> Message-ID: <200806262219.31766.hselasky@c2i.net> On Thursday 26 June 2008, Torfinn Ingolfsen wrote: > Hi, > > On Mon, Jun 23, 2008 at 12:01 AM, Hans Petter Selasky wrote: > > Hi again, > > > > I think this issue has been fixed, but you need to use to stuff from SVN. > > The 1.5.10 package is too old! And you need to use FreeBSD 6+ . > > Ok, I finally got the old machine[1] upgraded to FreeBSD 6.3-stable, > and installed the latest ISDN4BSD from svn (revision 755). > Both isdntrace and isdndecode still uses the new output format > (text-formatted hexdump with annotations). I tried all switches / > options on isdndecode but couldn't get it to output the old text > format. Is there something I have overlooked? > > To be precise, the call-logd script expects strings like the following > (it greps for them): > called party number: 99999999 > calling party number: 99999999 > > where '99999999' will be the actual number calling / called. > > Is it possible to get either isdntrace or isdndecode to output that format? > References: > 1) machine used: http://tingox.googlepages.com/dp686t3_freebsd Hi Torfinn, I think I patched "isdnd" some time back. The logfiles from "isdnd" should have that format. BTW: It is not very difficult to write a small CAPI 2.0 application that listens for calls and then prints them out in any format you like. I can make such an application in no time. How about "capimonitor" ? --HPS From tingox at gmail.com Thu Jun 26 22:30:09 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Thu Jun 26 22:30:12 2008 Subject: isdntrace - getting old output format back? In-Reply-To: <200806262219.31766.hselasky@c2i.net> References: <200806230001.37104.hselasky@c2i.net> <200806262219.31766.hselasky@c2i.net> Message-ID: Hi, On Thu, Jun 26, 2008 at 10:19 PM, Hans Petter Selasky wrote: > I think I patched "isdnd" some time back. The logfiles from "isdnd" should > have that format. OK, so the answer to my question is "no, you can't get the old output format back". Well, I'll have to change the call-logd script then. > BTW: It is not very difficult to write a small CAPI 2.0 application that > listens for calls and then prints them out in any format you like. I can make > such an application in no time. How about "capimonitor" ? So I'll end up with isdnd + capimonitor instead of isdnd + isdntrace? As long as it doesn't add complexity to the setup, I would be happy to have capimontor. And grateful. I will have to chenge the call-logd script anyway. -- Regards, Torfinn Ingolfsen From volker at vwsoft.com Thu Jun 26 22:59:01 2008 From: volker at vwsoft.com (Volker) Date: Thu Jun 26 22:59:06 2008 Subject: isdntrace - getting old output format back? In-Reply-To: References: <200806230001.37104.hselasky@c2i.net> <200806262219.31766.hselasky@c2i.net> Message-ID: <48641ACB.6000601@vwsoft.com> On 06/27/08 00:30, Torfinn Ingolfsen wrote: > Hi, > > On Thu, Jun 26, 2008 at 10:19 PM, Hans Petter Selasky wrote: >> I think I patched "isdnd" some time back. The logfiles from "isdnd" should >> have that format. > > OK, so the answer to my question is "no, you can't get the old output > format back". > Well, I'll have to change the call-logd script then. > >> BTW: It is not very difficult to write a small CAPI 2.0 application that >> listens for calls and then prints them out in any format you like. I can make >> such an application in no time. How about "capimonitor" ? > > So I'll end up with isdnd + capimonitor instead of isdnd + isdntrace? > As long as it doesn't add complexity to the setup, I would be happy > to have capimontor. And grateful. > > I will have to chenge the call-logd script anyway. > Torfinn, so, you're upgrading your OS, changing the i4b subsystem and doing a lot of other stuff to just not change a script? ;) Anyway, I've never tried HPS' isdn4bsd but if isdnd is nearly compatible, you may want to try to use the regexpr/regprog functionality and call your script (or a wrapper for it) from there. Volker From tingox at gmail.com Fri Jun 27 07:01:01 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Fri Jun 27 07:01:04 2008 Subject: isdntrace - getting old output format back? In-Reply-To: <48641ACB.6000601@vwsoft.com> References: <200806230001.37104.hselasky@c2i.net> <200806262219.31766.hselasky@c2i.net> <48641ACB.6000601@vwsoft.com> Message-ID: Hi On Fri, Jun 27, 2008 at 12:40 AM, Volker wrote: > so, you're upgrading your OS, changing the i4b subsystem and doing a lot > of other stuff to just not change a script? ;) It may look like that now, but it was sort of the other way around. :-) This machine was running 5.3 / 5.4-prerelease. Once that "branch" was EOL'ed (ok, some time after in fact) it got harder to support the ports on the machine, as the ports infrastructure remove support for unsupported branches (which is very wise, I might add). So I was really looking to upgrade the os (and the ports) on the machine anyway. HPS' ISDN4BSD stack has always been needed to support my isdn card. I was just trying to do as little as I could by just upgrading to 5.5-stable. Had I known that I would get hit by these changes, I would just have backed up the database and installed 6.3-stable directly, it would have saved some time. The machine is running callid[1] (which is where the call-logd script comes from) and a few other ports. > Anyway, I've never tried HPS' isdn4bsd but if isdnd is nearly > compatible, you may want to try to use the regexpr/regprog functionality > and call your script (or a wrapper for it) from there. calling the script isn't the problem. call-logd calls isdntrace and reads the output from it. The problem is that somewjere along the development path for HPS' isdn4bsd stack, the output format of isndtrace changed from a pure text-based output (which is easily parsed by a program) to a text formatted "hexdump with annotations" format which is much harder to parse. Anyway, now the machine is upgraded to 6.3-stable and HPS has offered to "fix" the isdn4bsd stack - we'll see how it goes. It seems like I will be submitting a PR for a change to the callid port in the near future. References: 1) callid - http://www.freshports.org/misc/callid/ -- Regards, Torfinn Ingolfsen, Norway