Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: morris@jade.jpl.nasa.gov.jpl.nasa.gov (Mike Morris)
Newsgroups: comp.dcom.telecom
Subject: Re: COCOTs and Long Distance
Message-ID: <4608@accuvax.nwu.edu>
Date: 2 Mar 90 05:24:49 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 24
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 136, Message 2 of 7

>I have had the same problem with COCOTs not accepting 10288 when I
>have wanted to use AT&T.  I thought of a solution that works -- if the
>COCOT accepts incoming calls, and, unfortunately, many do not.  If you

I've found out why - I think.  When the local supermarket replaced
their WeCo with a overpriced COCOT, I noticed the top of the dialing
info card said: "This phone does not accept incoming calls".  Well, I
noted the number of the phone and called it from my house: answered on
the 1st ring, but dead silence.  Hmmmmm - I fired up my XT and called
it with my 2400 baud modem in reverse mode (i.e. sending tones).
Ring, Ring, <click> and the pay fone responded with tones!  I got a
handshake and 16 characters of 80h (128 decimal).  I'm not that up on
protocols, but I think that's a file transfer request in one of the
popular protocols....

Maybe one of the more knowledgeable people will take this info and
have some fun....  oops - I mean perform a public service and correct
some of the mis-programmed phones - enable 800-, 10288-, etc...


Mike Morris                      Internet:  Morris@Jade.JPL.NASA.gov
                                 Misslenet: 34.12 N, 118.02 W
#Include quote.cute.standard     Bellnet:   818-447-7052
#Include disclaimer.standard     Radionet:  WA6ILQ