Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!mips!pacbell.com!lll-winken!telecom-request From: johnl@iecc.cambridge.ma.us (John R. Levine) Newsgroups: comp.dcom.telecom Subject: Re: AT&T's Call Manager: Security Problem? Message-ID: Date: 13 May 91 03:57:45 GMT Sender: Telecom@eecs.nwu.edu Organization: I.E.C.C. Lines: 25 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 356, Message 3 of 12 Being an inquisitive sort of guy, I investigated call manager codes from pay phones the moment I heard about them. Around here (Cambridge Mass, New England Tel territory) a 15XX code entered on a payphone on an AT&T call gets a quick recording that the service I have requested is not available and it hangs up. On NET calls, as soon as I dial 15 it cuts in with a recording reminding me to dial 11 for collect, 12 for third party, the card number for a calling card call, or 0 for an operator. Via MCI or Sprint, they don't know from call manager, but they do know that it isn't a valid card number, since no Bellcore-format calling card number or PIN starts with a 1. (Note that 0 + number via MCI or Sprint only accepts a local telco card number, not an MCI or FON card number, unless you fall through to the operator and let her enter it manually at extra cost. Don't ask me why.) The COCOTs around here are always broken, I don't know what they are supposed to do with call manager codes. Regards, John Levine, johnl@iecc.cambridge.ma.us, {spdcc|ima|world}!iecc!johnl