Re: use OpenBSD to blacklist phone calls?
make some money at it. http://killthecalls.com/ On 3/20/07, Paul Pruett <[EMAIL PROTECTED]> wrote: OpenBSD spamd works great for blacklisting IPs, and maybe it could be use for our blacklisting telephone calls using callerID? Even though we are on the 'do not call' registry we still get 4-10 calls a day at home, and at work its just phone spam spam spam Thinking about adding a modem that recognizes callerID to my home openbsd firewall/server to have it also monitor the phones and intercept telemarketing calls between ring 1 and 2 and if a match then give a false fax signal, message or just hangup signal. Has anyone else setup an openbsd server to hangup phone calls by callerid? I looked through /usr/ports/comms and /usr/ports/telephony I think this could be done with the port package asterisk, but it does look complex and I wondered if another package was more appropriate than a VOIP package? I did google some notes for [EMAIL PROTECTED] but I did not read that it is the same as the port ASTERISK. -TIA.
Re: use OpenBSD to blacklist phone calls?
Paul Pruett <[EMAIL PROTECTED]> writes: > OpenBSD spamd works great for blacklisting IPs, > and maybe it could be use for our blacklisting > telephone calls using callerID? Hm.. greylisting. Respond to the call with "please call back in 5 minutes" and if they don't blacklist them. //art
Re: use OpenBSD to blacklist phone calls?
use zapteller() [ page 115 ] and / or anti-girlfriend-logic [ page 104 ] as documented in the Asterisk - the future of Telephony. The asterisk book is available online via: http://www.asteriskdocs.org/modules/tinycontent/index.php?id=11 enjoy. Mark On 20/03/07, Paul Pruett <[EMAIL PROTECTED]> wrote: > > OpenBSD spamd works great for blacklisting IPs, > and maybe it could be use for our blacklisting > telephone calls using callerID? > > Even though we are on the 'do not call' registry > we still get 4-10 calls a day at home, and > at work its just phone spam spam spam > > Thinking about adding a modem that recognizes callerID > to my home openbsd firewall/server to have it also > monitor the phones and intercept telemarketing > calls between ring 1 and 2 and if a match then > give a false fax signal, > message or just hangup signal. > > Has anyone else setup an openbsd server to hangup > phone calls by callerid? > > I looked through /usr/ports/comms > and /usr/ports/telephony I think this could be > done with the port package asterisk, but it does > look complex and I wondered if another package > was more appropriate than a VOIP package? > > I did google some notes for [EMAIL PROTECTED] > but I did not read that it is > the same as the port ASTERISK. > > -TIA.
Re: use OpenBSD to blacklist phone calls?
On 2007/03/20 17:25, mark reardon wrote: > use zapteller() [ page 115 ] and / or anti-girlfriend-logic [ page 104 ] as > documented in the Asterisk - the future of Telephony. > > The asterisk book is available online via: it's in ports/packages now - /usr/ports/books/AsteriskTFOT
Re: use OpenBSD to blacklist phone calls?
Artur Grabowski wrote: Paul Pruett <[EMAIL PROTECTED]> writes: OpenBSD spamd works great for blacklisting IPs, and maybe it could be use for our blacklisting telephone calls using callerID? Hm.. greylisting. Respond to the call with "please call back in 5 minutes" and if they don't blacklist them. if it's an important phone call from a known contact perhaps having a code to bypass it would be a good idea. if you hand out your business card and someone is busy and can't make the 2nd phone call, they get blacklisted :( phone calls tend to be a bit more time-sensitive than emails in my experience. cheers, jake //art
Re: use OpenBSD to blacklist phone calls?
On 2007/03/20 16:10, Paul Pruett wrote: > > I looked through /usr/ports/comms > and /usr/ports/telephony I think this could be > done with the port package asterisk, Not without additional hardware (or porting your phone number to a voip gateway provider, if you can do such a thing where you live) > but it does > look complex and I wondered if another package > was more appropriate than a VOIP package? mgetty might have something useful - see http://home.leo.org/~doering/mgetty/mgetty_15.html > I did google some notes for [EMAIL PROTECTED] > but I did not read that it is > the same as the port ASTERISK. [EMAIL PROTECTED] (now renamed trixbox) is a CentOS-based linux distribution with pre-installed Asterisk and supporting pieces. I'll take the opportunity to point out that {3.9,4.0}-stable ports trees have just had an update to Asterisk to fix a remote (unauthenticated user) chan_sip vulnerability (-current has had 1.2.16 since shortly after unlock). Packages later.
Re: use OpenBSD to blacklist phone calls?
nice one. thanks. On 20/03/07, Stuart Henderson <[EMAIL PROTECTED]> wrote: > > On 2007/03/20 17:25, mark reardon wrote: > > use zapteller() [ page 115 ] and / or anti-girlfriend-logic [ page 104 ] > as > > documented in the Asterisk - the future of Telephony. > > > > The asterisk book is available online via: > > it's in ports/packages now - /usr/ports/books/AsteriskTFOT
Re: use OpenBSD to blacklist phone calls?
I wish there was a OpenBSD based article on How to Setup a Small Office on Asterisk. I would Try it. Sam Fourman Jr. On 3/20/07, mark reardon <[EMAIL PROTECTED]> wrote: nice one. thanks. On 20/03/07, Stuart Henderson <[EMAIL PROTECTED]> wrote: > > On 2007/03/20 17:25, mark reardon wrote: > > use zapteller() [ page 115 ] and / or anti-girlfriend-logic [ page 104 ] > as > > documented in the Asterisk - the future of Telephony. > > > > The asterisk book is available online via: > > it's in ports/packages now - /usr/ports/books/AsteriskTFOT
Re: use OpenBSD to blacklist phone calls?
What Would you do in the case of Telemarketers using caller ID block (*69 for my Phone Company) I get 2 or 3 calls a week From some stupid bank wanting to refinance a mortage all of these calls come up Restricted or Private on Caller ID. Sam Fourman Jr. On 3/20/07, Jacob Yocom-Piatt <[EMAIL PROTECTED]> wrote: Artur Grabowski wrote: > Paul Pruett <[EMAIL PROTECTED]> writes: > > >> OpenBSD spamd works great for blacklisting IPs, >> and maybe it could be use for our blacklisting >> telephone calls using callerID? >> > > Hm.. greylisting. Respond to the call with "please call back in 5 > minutes" and if they don't blacklist them. > > if it's an important phone call from a known contact perhaps having a code to bypass it would be a good idea. if you hand out your business card and someone is busy and can't make the 2nd phone call, they get blacklisted :( phone calls tend to be a bit more time-sensitive than emails in my experience. cheers, jake > //art
Re: use OpenBSD to blacklist phone calls?
On Tue, Mar 20, 2007 at 01:34:29PM -0500, Sam Fourman Jr. wrote: > What Would you do in the case of Telemarketers using caller ID block > (*69 for my Phone Company) > > I get 2 or 3 calls a week From some stupid bank wanting to refinance a > mortage all of these calls come up Restricted or Private on Caller ID. please don't confuse greylisting with PTR checks. they're totally different things. :) :) :) :) :) -- jared
Re: use OpenBSD to blacklist phone calls?
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Sam Fourman Jr. > Sent: Tuesday, March 20, 2007 2:34 PM > To: Jacob Yocom-Piatt > Cc: misc@openbsd.org > Subject: Re: use OpenBSD to blacklist phone calls? > > What Would you do in the case of Telemarketers using caller ID block > (*69 for my Phone Company) > > I get 2 or 3 calls a week From some stupid bank wanting to refinance a > mortage all of these calls come up Restricted or Private on Caller ID. > > Sam Fourman Jr. > Some phone companies have a service where you need a four digit code to complete the call. My friend has this, after the first ring you here a recording that says something like, this number is currently unavailable or something to that effect. If you punch in the special code you connect pass this. I think it's a few dollars a month and you can setup a white list so some numbers don't need the code.
Re: use OpenBSD to blacklist phone calls?
On 3/20/07, mark reardon <[EMAIL PROTECTED]> wrote: use zapteller() [ page 115 ] and / or anti-girlfriend-logic [ page 104 ] as Why would any geek want this? ^^
Re: use OpenBSD to blacklist phone calls?
On Tue, Mar 20, 2007 at 01:37:17PM -0500, Sam Fourman Jr. wrote: > I wish there was a OpenBSD based article on How to Setup a Small > Office on Asterisk. I would Try it. Why? Just pick any of the numerous Asterisk tutorials, and engage your brain before typing. The differences are minimal, and mostly of the variety 'Debian uses /usr/bin/asterisk and OpenBSD uses /usr/local/bin/asterisk'. Still, from a safe distance, asterisk appears to overcomplicated, insecure, and buggy. Not sure if that impression changes on a closer look, but I've no reason to find out. Joachim
Re: use OpenBSD to blacklist phone calls?
mgetty might have something useful - see http://home.leo.org/~doering/mgetty/mgetty_15.html thanks. Hmm, maybe it can be as simple as setting up fax support for just the black list. From what I read on your link, it suggests the configuration can be set to only accept for specified numbers. That way the listed phone numbers for telemarkers could get a fax response which can be really annoying. The next step may be to send any fax responses to /dev/null I just ordered a Wildcard X100P card for $5.95 through googlebase and started the build for /usr/ports/comms/mgetty+sendfax Maybe late next week I can try this approach and report back.
Re: use OpenBSD to blacklist phone calls?
SUCCESS the package mgetty+sendfax can be used to intercept phone calls by callerID using fax answer after modification to port mgetty+sendfax --- notes --- I had ordered a generic modem for asterisk usage, but was warned that it may need "Zaptel" support by a subscriber, so that was a wasted $6 + $9 shipping, so I went back to the scrounge pile and found in an old external USR modem that supported callerID, AT#CID=1 After a modem relearning curve I got mgetty+sendfax running Some tips: # grep cua /etc/ttys cua00 "/usr/local/sbin/mgetty"vt100 on insecure #to pickup changes to /etc/ttys kill -1 1 #And you make config changes and want to make #sure mgetty picks them up you can kill the mgetty PID #and /sbin/init will restart it. HOWever... mgetty from the port package would ignore the configuration file /etc/mgetty+sendfax/dialin.config I discovered the port package needs to also uncomment a line in the default policy.h file the line to use dialin.config. If you look at the used policy.h files you will see /* #define CNDFILE "dialin.config" */ I found the existing patch that already touches the file, /usr/ports/comms/mgetty+sendfax/patches/patch-policy_h_dist And I edited out the comment on that line and remade the patch, diff -u and saved result over patch-polich_h_dist (also attached to this email) Then I removed the package, and port working directory and make package. IT WORKS now. I'll send an email to port maintainer about it. If someone see how this becomes a security issue to enable, please inform. ... So in conclusion I implemented this on OPENBSD 4.0, and if you want to use the callerID feature mgetty+sendfax... http://home.leo.org/~doering/mgetty/mgetty_15.html#SEC15 You will have to recompile after modifying policy.h I added "none" for UNKNOWN callerids and some recent pesty callerIDs and the "!all" at end of the dialin.config file and its so sweet to have the fax answer the telemarketers. It looks like mgetty.config has hooks and could use external resources to phonenumbers to block, so some of the jokes about using something like spamd-setup may be feasible :) but for now I can edit /etc/mgetty+sendfax/dialin.config and mgetty reads the text file changes w/o hangup signal or restarting the process. Enjoy. ps., be sure to verigy your modem has support for callerID, http://ftp.mtnsys.com/pages/howto/htmdmtst.htm --- policy.h-dist.orig Wed Feb 22 13:56:31 2006 +++ policy.h-dist Fri Mar 23 15:10:41 2007 @@ -48,7 +48,7 @@ * Normally, this is "/bin/login", just a few systems put "login" * elsewhere (e.g. Free/NetBSD in "/usr/bin/login"). */ -#define DEFAULT_LOGIN_PROGRAM "/bin/login" +#define DEFAULT_LOGIN_PROGRAM "/usr/bin/login" /* FidoNet mailer support * @@ -85,7 +85,7 @@ * ZyXELs use S40.2=1. * If the path doesn't start with "/", it's relative to CONFDIR. */ -/* #define CNDFILE "dialin.config" */ +#define CNDFILE "dialin.config" /* If you want to use /etc/gettydefs to set tty flags, define this @@ -114,7 +114,7 @@ /* group id that the device is chown()ed to. If not defined, the * primary group of "DEVICE_OWNER" is used. */ -#define DEVICE_GROUP "modem" +#define DEVICE_GROUP "dialer" /* access mode for the line while getty has it - it should be accessible * by uucp / uucp, but not by others (imagine someone dialing into your @@ -249,7 +249,7 @@ # ifdef linux # define LOCK "/var/lock/LCK..%s" # endif -# if defined(__FreeBSD__) || defined(__NetBSD__) +# if defined(__FreeBSD__) || defined(__NetBSD__) || defined(__OpenBSD__) # define LOCK "/var/spool/lock/LCK..%s" # endif #endif @@ -564,7 +564,7 @@ #endif #ifndef MAILER -# define MAILER"/usr/lib/sendmail" +# define MAILER"/usr/sbin/sendmail" # define NEED_MAIL_HEADERS #endif