Path: utzoo!telecom-request Date: Wed, 1 May 91 9:18:58 EDT From: Carl Moore (VLD/VMB) Newsgroups: comp.dcom.telecom Subject: Re: New Area Code Won't Work From Hotel Message-ID: 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 11, Issue 330, Message 8 of 9 Lines: 27 To summarize, there are sometimes problems in reaching new area codes or prefixes. It makes you wonder about which poor souls will end up in the first NNX area code. From 1973 to 1980, there may have been problems in making calls from the U.S. east coast to prefixes of N0X/N1X form in area 213 (Los Angeles etc.; currently 213/818, and later to become 213/818/310). At least there would have been a problem in explaining it to operators on the east coast, with such problem going away only when NYC got N0X/N1X prefixes. Someone in this Digest complained of people having trouble reaching him in the then-new area code 508 in Massachusetts; it split from 617 in 1988. Several years ago, I had to ask an operator to make a call for me to a new prefix (301-850), because my attempt to make a 0+ call to it did not work (0-850-xxxx, the correct syntax at the time for 0+ within Maryland when originating outside the DC area). And I know of someone who had trouble reaching 202-994. This Digest also had a complaint last year about someone not being able to complete a local call of the form NPA + 7D from a hotel (in the VA suburbs of DC) to either MD or DC. In this case, he had to work around by using 7D, which still worked at the time.