home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!telecom-request
- Date: Sun, 15 Nov 92 14:56:32 CST
- From: mearle@pro-party.cts.com
- Newsgroups: comp.dcom.telecom
- Subject: New Area Code Blitzes Cell Phone User
- Message-ID: <telecom12.852.2@eecs.nwu.edu>
- Organization: TELECOM Digest
- Sender: Telecom@eecs.nwu.edu
- Approved: Telecom@eecs.nwu.edu
- X-Submissions-To: telecom@eecs.nwu.edu
- X-Administrivia-To: telecom-request@eecs.nwu.edu
- X-Telecom-Digest: Volume 12, Issue 852, Message 2 of 14
- Lines: 29
-
- This last weekend (November 7) a friend and I were in Houston
- attending a conference. He is from San Antonio, which the week prior
- had officially cut over to area code 210 (from 512). He dutifully went
- and had his portable cmt reprogrammed, and reports calls in and out
- worked fine all week while in San Antonio.
-
- Upon arriving in Houston, he tried to make some calls, but got
- constant reorder -- no message. Upon checking with customer service,
- it turns out that GTE Mobilnet hadn't updated "something" and believed
- his phone number and esn not to match the data base, and thereby
- denied him service. He was unable to use his phone the entire weekend.
- No one in CS seemed to be able to do anything for him; it "might" be
- fixed by Monday, they said.
-
- Seems like, with over a year's advance notification of the exact date,
- and all the publicity, *someone* at GTE Mobilnet would have considered
- this and done whatever updates were required.
-
- Oh well. At least my phone (on the same carrier as my friend's,
- Southwestern Bell Mobile Systems) worked, since my home area, Corpus
- Christi, did not change with the new A/C.
-
-
- mearle@pro-party.cts.com (Mark Earle) [WA2MCT/5]-= +
- FidoNet at Opus 1:160/50.0
- Bitnet adblu001@ccsu.vm1
- Internet 73117.351@compuserve.com
-
-