Path: utzoo!attcan!uunet!cs.utexas.edu!wuarchive!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: parker@epiwrl.epi.com (Alan Parker)
Newsgroups: comp.dcom.telecom
Subject: Re: 202 Area Code Shrinks to DC Proper
Message-ID: <12968@accuvax.nwu.edu>
Date: 3 Oct 90 03:00:26 GMT
Sender: news@accuvax.nwu.edu
Reply-To: Alan Parker <parker@epiwrl.epi.com>
Organization: Entropic Research Laboratory, Inc., Washington, DC
Lines: 22
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 6 of 14


In article <12908@accuvax.nwu.edu> cmoore@brl.mil (VLD/VMB) writes:
X-Telecom-Digest: Volume 10, Issue 703, Message 15 of 15

>Today, Oct. 1, 1990, is scheduled as full cutover for NPA+7D local
>calls in DC area if you are calling across the areacode boundary.

>Now, 202 area has been shrunk (although no new area code has been
>created), and the above instruction is now:
>1+301+7D

>All of the above goes for the Va. suburbs, with 703 substituted for 301.

Not quite.  For calls within the DC metro dialing area, you do not
dial the leading one.  So to call from DC to Silver Spring, MD, you
dial 301-589-XXXX.  Note the metro dialing area includes parts of
three area codes.  The intention is that if you need to dial the
leading 1, then the call is costing you a toll.

As of this writing, I can still call from my office in DC
(202-547-xxxx) to home in MD (301-870-xxxx) without dialing 301.  I
guess they can't reprogram all the switches over night!