Path: utzoo!news-server.csri.toronto.edu!rutgers!cbmvax!bagate!dsinc!telecom-request From: CAPEK%YKTVMT.BITNET@cunyvm.cuny.edu (Peter G. Capek) Newsgroups: comp.dcom.telecom Subject: Still More COCOT Sleaze Message-ID: Date: 13 Mar 91 23:28:56 GMT Sender: Telecom@eecs.nwu.edu Organization: TELECOM Digest Lines: 18 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 201, Message 4 of 4 In late January, I was visiting Washington, DC. I was forced to use a COCT in the basement of the hotel at which I was staying, and had an bizarre experience which I had intended to write about here, but never got around to. It is that I was unable to use 10288 to use AT&T, but, 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've just gotten the phone bill for that period and discover the call shown as provided by an AOS ($6+ for five minutes, less than fifty miles) and NOT by AT&T. I wish I had written down at the time exactly what happened when I made the call, but the appearance is that of the AOS identifying itself as AT&T. Has anyone else experienced this? Peter Capek