TIP: Click on subject to list as thread! ANSI
echo: aust_modem
to: All
from: John Piper
date: 1996-12-02 20:31:26
subject: Courier on the fritz

Last week, and just five minutes ago, I discovered that my Courier would
not answer any inbound calls. Several tests with my other line and mobile
proved that there was a definite problem. The auto-answer LED on my
Courier's panel would flash while the line was ringing, but my mailer would
fail to show any signs of a RING signal. Jumping into terminal mode, I
dialled my line again. ASCII garbage of equal amounts would echo to the
screen in place of a RING.

In both cases, I found that rewriting the modem's profile
(AT&F1&K3) did the trick and fixed the problem; the Courier would
once again recognise RING and answer the call. I have no idea why this
suddenly started happening.

Anyone have any explanation for this odd behaviour? Could it be a fault
with NVRAM? I'd be interested in hearing people's thoughts on the matter. I
don't particularly want to rewrite my modem's profile regularly.

John (japp{at}mpx.com.au)

--- FMail/386 1.22+
* Origin: Lateline BBS, Sydney; +61-2-9579-6564; 24 hours; 33.6k (3:712/841)
SEEN-BY: 50/99 620/243 623/630 711/401 409 410 413 430 808 809 899 932 934
SEEN-BY: 712/311 407 505 506 515 517 624 628 704 824 841 888 713/317 714/906
SEEN-BY: 772/20 800/1
@PATH: 712/841 624 515 711/808 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.