Path: utzoo!utgpu!watserv1!ria!uwovax.uwo.ca!telecom-request
From: cybrspc!roy@cs.umn.edu (Roy M. Silvernail)
Newsgroups: comp.dcom.telecom
Subject: Re: Still More COCOT Sleaze
Message-ID: <telecom11.208.7@eecs.nwu.edu>
Date: 16 Mar 91 04:39:06 GMT
Sender: Telecom@eecs.nwu.edu
Organization: Villa CyberSpace, Minneapolis, MN
Lines: 23
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 11, Issue 208, Message 7 of 14

CAPEK%YKTVMT.BITNET@cunyvm.cuny.edu (Peter G. Capek) writes:

>  when I dialed 0, expecting to get either AOS/COCOT operator, after a
>  LOT of delay and clicking, I got an operator who identified himself as
>  being "AT&T".  That seemed strange, but I accepted it.  I billed the
>  call to my AT&T card number.

I'd bet that, if you pressed the operator, you'd find that s/he was
saying "ATNT" instead of 'AT&T'.

I steer clear of COCOTs for long distance. Here in Minneapolis, a fair
number of AT&T COCOTs are appearing, and I've used them for local
calls.  It's surprising, at first, since they hand you dial tone,
accept the number, and after a brief pause you hear another dial tone
and the number you dialled being pulsed out.  When the second blast of
dial tone comes on, it sounds strange by comparison. (The locally
generated DT you get at first isn't quite a match for DT from the CO.)

I haven't checked the keypad to see if it remains active. (I'll do that
next time I see one of these phones.)


Roy M. Silvernail |+|  roy%cybrspc@cs.umn.edu