Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: cmoore@brl.mil (VLD/VMB)
Newsgroups: comp.dcom.telecom
Subject: Re: 215 to Join the N0X/N1X World
Message-ID: <12752@accuvax.nwu.edu>
Date: 28 Sep 90 14:08:18 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 15
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 691, Message 5 of 12


Local calls WITHIN 215 are and will remain seven digits.  Local calls
from 215 to outside of 215 are 1+NPA+7D and will stay that way.
(Someone -- was it JSol? -- sent me a note about trying a local call
from Pa. to Del. leaving off the 1+ and just using 302+7D in, this
case, the 215-255 exchange at Kemblesville, Chester County; won't this
have to be "cleaned up"? and the 1+ required?)

Didn't you see my message about the local service from Lehighton
(215-377) to Jim Thorpe (717-325)?  That's 1+717-325-xxxx.

Years ago, I noticed no 1+ in the calling instructions for Pittsburgh
(i.e. all calls within 412 were 7D, with NPA+7D for calls outside of
412, with Pittsburgh being too far from NPA line to have local service
to another NPA).  Is 412 now short of empty prefixes?