Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!wuarchive!texbell!vector!telecom-gateway From: opel!johnk@uunet.uu.net (John Kennedy) Newsgroups: comp.dcom.telecom Subject: Re: Incorrect Use of Area Code 202 Message-ID:Date: 15 Aug 89 12:35:27 GMT Sender: news@vector.Dallas.TX.US Reply-To: johnk@opel.UUCP (John Kennedy) Organization: Second Source, Inc., Annapolis, MD Lines: 28 Approved: telecom-request@vector.dallas.tx.us X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@vector.dallas.tx.us X-TELECOM-Digest: volume 9, issue 301, message 8 of 10 In article cmoore@brl.mil (VLD/VMB) writes: >X-TELECOM-Digest: volume 9, issue 296, message 4 of 8 >I have seen 2 recent cases where area code 202 was used in front of a Maryland >number which has metro DC-area service but is beyond area 202 (they are only >in area 301). In one case, 202-621 was displayed on the back of a panel >truck. In the other case, 202-261 was displayed in a fast-food restaurant in >an employment ad. It's my understanding that that's supposed to work, since the numbers in the metro DC area are "local" to one another, even though they may be in area codes 202, 703 or 301. Now, not all of the exchanges in 703 and 301 are local calls in the DC area, but the ones that are local are dialable with the 202 area code. For example, my home phone exchange is 858. It's in distant Maryland, but is one of the exchanges with the privelege of being local to DC and is dialable (from outside the area) with a 202 area code. Likewise, phones in Northern Virginia (703 are code) are also dialable with 202. The US-gov't FTS service didn't used to support 703 or 301 for the DC suburbs. You always dialed 202. John Kennedy johnk@opel.UUCP Second Source, Inc. Annapolis, MD