Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!gatech!rutgers!netsys!vector!nobody From: daisy!bob@stl.olivetti.com (Bob Weissman) Newsgroups: comp.dcom.telecom Subject: Re: Calling card silliness Message-ID: Date: 7 Dec 88 23:48:58 GMT Sender: chip@vector.UUCP Organization: Olivetti Software Technology Laboratory, Menlo Park, CA Lines: 23 Approved: telecom-request@vector.uucp X-Submissions-To: telecom@bu-cs.bu.edu X-Administrivia-To: telecom-request@vector.uucp X-TELECOM-Digest: volume 8, issue 198, message 6 In article , kent@wsl.dec.com writes: - Three weeks ago, we moved. We moved a total of about 10 blocks; we're - in the same service area (415-641, Pacific Bell), and kept the same - number. - - What I didn't expect was that my calling card would stop working. Seems - that any change in service causes them to cancel the current card. If - you're lucky, they'll automagically order you a new one (with a - different PIN) -- but usually you have to notice that your card is not - working and request a new one. This is interesting. I also recently moved within my service area (415-967) and kept the same number, and my Pacific Bell calling card still works fine, as does my AT&T card with the same number. Sounds like someone simply screwed up. Of course, I only moved about six blocks... -- Bob Weissman bob@stl.olivetti.com Routed UUCP: bob@oli-stl.uucp UUCP: ...!{ ames | decwrl | oliveb | pyramid }!oli-stl!bob Arpanet: bob%oli-stl.uucp@ames.arc.nasa.gov