From: John Floren <john@jfloren.net>
To: Chris Hanson <cmhanson@eschatologist.net>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Anyone have a modem wired up?
Date: Wed, 27 Oct 2021 18:29:59 +0000 [thread overview]
Message-ID: <hVNrWEDc6WJqGY4EFFCZUmrG0kAG5PzVkSPPmpcNiCid9VMTVKTGqjYbuTgpOkn97bOnQzCQD1LD0wEGBjYvrOSHWE63oqa0PX12DqTtAFQ=@jfloren.net> (raw)
In-Reply-To: <81D078E9-072B-4969-BCA2-A71975D304EE@eschatologist.net>
On Wednesday, October 27th, 2021 at 11:17 AM, Chris Hanson <cmhanson@eschatologist.net> wrote:
> Obihai makes some decent, cheap-on-eBay, unlockable/hackable analog VoIP boxes that work just fine with not-super-fast modems. You won’t get 56K or even 33.6, but 9600-14.4K should be fine and a Telebit Trailblazer probably would be too if you want to use UUCP over dialup…
>
> — Chris
I've got a Grandstream HT801 through my ISP (Sonic.net) which works fine for voice, and it previously did ok with the modem, but now when I try, I start to get garbage soon after the connection establishes (see http://jfloren.net/noise.jpg for an example). It happens regardless of who I connect to, and seemingly without regard for the connection speed--although at 9600, the garbage fills up the screen quite rapidly compared to a rather sedate trickle at 4800.
My modem-fu is rather weak, so if anyone recognizes what's going on, please let me know. I worry that it's just a noisy phone connection, but I was under the impression that modems had some sort of error-correction built in (this is a SupraFaxModem 288).
john
next prev parent reply other threads:[~2021-10-27 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 23:43 John Floren
2021-10-24 0:56 ` Warner Losh
2021-10-24 1:29 ` Kenneth Goodwin
2021-10-24 15:36 ` Dan Cross
2021-10-24 16:14 ` Jon Steinhart
2021-10-24 16:37 ` Larry Stewart
2021-10-24 16:51 ` Dr Iain Maoileoin
2021-10-27 18:17 ` Chris Hanson
2021-10-27 18:29 ` John Floren [this message]
2021-10-27 18:51 ` Dan Cross
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='hVNrWEDc6WJqGY4EFFCZUmrG0kAG5PzVkSPPmpcNiCid9VMTVKTGqjYbuTgpOkn97bOnQzCQD1LD0wEGBjYvrOSHWE63oqa0PX12DqTtAFQ=@jfloren.net' \
--to=john@jfloren.net \
--cc=cmhanson@eschatologist.net \
--cc=tuhs@tuhs.org \
/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 NNTP newsgroup(s).