[comp.dcom.telecom] 202 Shrinks to DC Proper

cmoore@brl.mil (VLD/VMB) (10/04/90)

This replies to Alan Parker <parker@epiwrl.epi.com>.

Please don't take my remarks too far out of context.  Yes, I wrote:

>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.

But I also wrote

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

With "the above instruction" meaning the procedure for LONG DISTANCE
calls to the Md. suburbs (in text which you left out of your reply).

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

Again, this refers to LONG DISTANCE calls into the suburbs.

By the way, I wrote (in a different posting) that the leading 1+ is
optionally available for use on those local calls in DC area across
areacode boundaries.  It is REQUIRED if you are calling long distance
from the DC area, and is also required on certain local and extended-
area calls which have been eleven digits (due to prefix duplication);
those local and extended-area calls can reduce to seven digits after
the dust settles from the changes just made.

Please check to see if you can use 1+NPA+7D on the local call across
the areacode boundary, and if you can use 1+NPA+7D on the local call
within your own areacode (this is in the DC area).