Path: utzoo!attcan!uunet!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: nam2254%dsacg2.dsac.dla.mil@dsac.dla.mil (Tom Ohmer)
Newsgroups: comp.dcom.telecom
Subject: Re: MCI as Slamming King
Message-ID: <12966@accuvax.nwu.edu>
Date: 2 Oct 90 20:02:06 GMT
Sender: news@accuvax.nwu.edu
Organization: Defense Logistics Agency Systems Automation Center, Columbus
Lines: 17
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 707, Message 4 of 14


Tom Ohmer [O] and Chris Johnson [J] wrote in volume 10, issue 659:

< Robert Michael Gutierrez is the local expert on these matters, but
< I'll venture a theory: Tom's apartment-mate wanted MCI 1+ on his own
< line but 10222 access to his own MCI account if he should need to
< place a long-distance call from Tom's line, so he gave MCI both phone
< numbers with explicit instructions that his was to get primary service
< but Tom's was to get secondary service.

Nice guess, but wrong.  ;-) My aptartment-mate did/does not have it's
own line.  The primary service of *my* line was changed.

Tom Ohmer @ Defense Logistics Agency Systems Automation Center,
            DSAC-AMB, Bldg. 27-6, P.O. Box 1605, Columbus, OH  43216-5002
UUCP: ...osu-cis!dsac!tohmer   INTERNET: tohmer@dsac.dla.mil
Phone: (614) 238-8059   AutoVoN: 850-8059   #include <stdsclmr.h>