From hselasky at c2i.net Sat Oct 10 14:23:31 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Oct 10 14:23:39 2009 Subject: New version (1.7.4) of ISDN4BSD available Message-ID: <200910101524.19402.hselasky@c2i.net> Hi, I've uploaded a new version of my ISDN4BSD package at: http://www.selasky.org/hans_petter/isdn4bsd See the driver information page for a feature list. MD5 (releases/FreeBSD/1_7_4/Makefile) = a2f2c986d2bb2709932650df2a38405e MD5 (releases/FreeBSD/1_7_4/Makefile.v1) = 0f78dcddbeb854b845c31a2b74cefe05 MD5 (releases/FreeBSD/1_7_4/Makefile.v2) = de870c044ee30790d25ee319aa8baa53 MD5 (releases/FreeBSD/1_7_4/new_ihfc_1_7_4.diff.bz2) = 4059d198768f9f8dc9372dc1c54bc3c3 MD5 (releases/FreeBSD/1_7_4/new_ihfc_1_7_4.tar.bz2) = 3640949b5fac229a7c46762381a3117e fetch http://www.turbocat.net/~hselasky/isdn4bsd/releases/FreeBSD/1_7_4/Makefile fetch http://www.turbocat.net/~hselasky/isdn4bsd/releases/FreeBSD/1_7_4/Makefile.v1 fetch http://www.turbocat.net/~hselasky/isdn4bsd/releases/FreeBSD/1_7_4/Makefile.v2 fetch http://www.turbocat.net/~hselasky/isdn4bsd/releases/FreeBSD/1_7_4/new_ihfc_1_7_4.tar.bz2 fetch http://www.turbocat.net/~hselasky/isdn4bsd/releases/FreeBSD/1_7_4/new_ihfc_1_7_4.diff.bz2 --HPS From a-bauer at live.de Thu Oct 15 12:46:31 2009 From: a-bauer at live.de (Andreas Bauer) Date: Thu Oct 15 12:46:38 2009 Subject: Help with tool to reject callers Message-ID: Hi, I'm thinking of creating a little program to reject incoming calls on my isdn line, so that none of the phones on the line ring when there's an "unwanted" caller (based on their phone numbers). Since I'm using i4b's capimonitor to log incoming numbers already, and its code is quite simple, I want to base the program on that nice little tool. :-) Now, I'm not very experienced with the whole ISDN thing, so I hope that this is the right place to ask for a little help to start me off. First of all, is there a simple way to *totally* reject a call? "Totally rejecting" meaning that no other phones on the same S0 bus keep ringing? A CAPI_CALL_REJECT_*, which I tried first, obviously has no effect on all the other phones on the bus. If there is no way to easily reject the calls, then I guess the program would need to accept the call and immediately hang up again to achieve the same thing? Of course that might be a little ugly, since it might cost the caller money, but it would still be fine with me. In that case, what is the absolute minimum of steps that need to be taken to do this? I know that all the code for this should basically be in the capitest utility, but maybe there's an even shorter way to do this if you don't even really want to transfer anything. What parts of the message handler can also go? Thanks for the help already :-) Andreas _________________________________________________________________ http://redirect.gimas.net/?n=M0910xDateiensenden2 Fotos, Musik ?Dateien versenden ? ganz einfach, ohne Limit From hselasky at c2i.net Thu Oct 15 16:14:33 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Oct 15 16:14:40 2009 Subject: Help with tool to reject callers In-Reply-To: References: Message-ID: <200910151713.36080.hselasky@c2i.net> On Thursday 15 October 2009 14:34:30 Andreas Bauer wrote: > Hi, > > I'm thinking of creating a little program to reject incoming calls on > my isdn line, so that none of the phones on the line ring when there's > an "unwanted" caller (based on their phone numbers). > > Since I'm using i4b's capimonitor to log incoming numbers already, and > its code is quite simple, I want to base the program on that nice > little tool. :-) > > Now, I'm not very experienced with the whole ISDN thing, so I hope > that this is the right place to ask for a little help to start me off. > > First of all, is there a simple way to *totally* reject a call? > "Totally rejecting" meaning that no other phones on the same S0 bus > keep ringing? A CAPI_CALL_REJECT_*, which I tried first, obviously has > no effect on all the other phones on the bus. > > If there is no way to easily reject the calls, then I guess the > program would need to accept the call and immediately hang up again > to achieve the same thing? Of course that might be a little ugly, > since it might cost the caller money, but it would still be fine with > me. In that case, what is the absolute minimum of steps that need to > be taken to do this? > I know that all the code for this should basically be in the capitest > utility, but maybe there's an even shorter way to do this if you don't > even really want to transfer anything. What parts of the message > handler can also go? > Hi, I think the most efficient way, using a Point to Multipoint setup, is to answer the call and then hangup the call. Sometimes the RELEASE_COMPLETE messages are simply ignored in P2MP configurations before the call is answered. --HPS From hselasky at c2i.net Mon Oct 19 16:43:53 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Oct 19 16:44:00 2009 Subject: Analog phone adapter support coming for ISDN4BSD Message-ID: <200910191844.52068.hselasky@c2i.net> Hi, ISDN4BSD will soon ship with Yealink (USB to Analog Phone) and compatible adapter support. I4B has recently been extended to handle Analog Phones at the same level as ISDN phones, through a brand new DSS1 lite implementation. And still, only one channel driver for Asterisk, chan_capi, and one configuration tool, isdnconfig making your life even more easy :-) In that regard I would like to ask if anyone wants to sponsor a commonly used Analog adapter (USB or PCI) which they would like to have supported under I4B under FreeBSD(USB+PCI) / NetBSD(PCI only)? --HPS