freebsd-isdn Digest, Vol 241, Issue 1
freebsd-is...@freebsd.org
freebs...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
or, via email, send a message with subject or body 'help' to
freebsd-is...@freebsd.org
You can reach the person managing the list at
freebsd-i...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-isdn digest..."
Today's Topics:
1. Help with tool to reject callers (Andreas Bauer)
2. Re: Help with tool to reject callers (Hans Petter Selasky)
----------------------------------------------------------------------
Message: 1
Date: Thu, 15 Oct 2009 14:34:30 +0200
From: Andreas Bauer <a-b...@live.de>
Subject: Help with tool to reject callers
To: <freebs...@freebsd.org>
Message-ID: <SNT123-W1BE5560A6...@phx.gbl>
Content-Type: text/plain; charset="Windows-1252"
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
------------------------------
Message: 2
Date: Thu, 15 Oct 2009 17:13:35 +0200
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: Help with tool to reject callers
To: freebs...@freebsd.org
Message-ID: <200910151713....@c2i.net>
Content-Type: Text/Plain; charset="windows-1252"
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
------------------------------
End of freebsd-isdn Digest, Vol 241, Issue 1
********************************************