From: Jack Heim <jheim@facstaff.wisc.edu>
To: blinux-list@redhat.com
Subject: Re: modems
Date: Mon, 25 Mar 2002 09:33:06 -0600 [thread overview]
Message-ID: <5.1.0.14.2.20020325090602.00a7f270@facstaff.wisc.edu> (raw)
In-Reply-To: <3.0.6.32.20020323212729.008bbaa0@mail.doorpi.net>
My info on the issues you bring up is about 2 years old but I think it
probably is still correct... Your items 2-4 below depend on your software
and not on the modem. For software, I think you want to go with mgetty. You
can probably do the things you want to do through mgetty's caller ID
feature. You have to have caller ID on your phone line of course.
I did a little reading before I bought my modem and the prevailing wisdom
on the linux newsgroups was to use an external modem. An internal modem is
going to add a third com port to your machine. By default, com3 would be on
the same IRQ as com1. If you get an external modem, you can connect it to
com1 or com2 and avoid that problem.
A friend of mine has an internal modem in his machine and he got it to work
by disabling com2 on the motherboard and forcing the modem to use com2. I
don't know how he did that though and he's on spring break now so I can't
ask him. I think he did it via the Windows setup program that came with the
modem.
Anyway, I think you'll be able to do what you want through a combination of
an external modem and mgetty.
At 09:27 PM 3/23/02 -0600, you wrote:
>What is a good modem to get that works under linux that can do the following:
>1. voice/data/fax
>2. trace the calls coming in if it's on an inside line rather than an
>outside direct line, i.e you have to dial 9 to get an outside line.
>3. would allow me to hook my regular phone up to it
>4. would be able to block callers based on what number they call from.
>I use both windows and linux, and am on a lan there, but at home, I will
>have to go back to dialup again. I don't even use the modem in my system
>right now, but could hook it up for blocking calls if there's no other way
>but to let them go to voice mail and never answer any calls. *60 doesn't
>get in to a prompt to do it, and dialing 9*60 doesn't work either.
>Thanks.
>
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
modems Brent Harding
` Jack Heim [this message]
` modems Janina Sajka
` modems L. C. Robinson
` modems Brent Harding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.0.14.2.20020325090602.00a7f270@facstaff.wisc.edu \
--to=jheim@facstaff.wisc.edu \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).