Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: goudreau@dg-rtp.dg.com (Bob Goudreau)
Newsgroups: comp.dcom.telecom
Subject: Re: 215 Area Code Loses "1" per Newspaper 'Reporter'
Message-ID: <15572@accuvax.nwu.edu>
Date: 21 Dec 90 20:54:23 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
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 896, Message 3 of 7


In article <15537@accuvax.nwu.edu>, sba8_ltd@uhura.cc.rochester.edu
(Scott Barnes) writes:

> I have heard from a different source that Bell of PA intends to
> implement exchange codes of the type "XXX", so that exchanges such as
> 131 will now be possible. 

I think you must have mis-heard this one.  NXX, yes; but I won't
believe XXX.  Using your "131" example above, there would be ambiguity
when the telco received the dialling sequence 1312555.  Unless it used
a timeout (yuck!), the switch would be unable to distinguish between a
local call to 131-2555 and a LD call to Chicago of the form
1-312-555-XXXX.  The whole point of cleaning up dialling rules (as
Bell of PA is doing now in 215) is to allow NXX exchanges *without*
ambiguity or timeouts.


Bob Goudreau				+1 919 248 6231
Data General Corporation		goudreau@dg-rtp.dg.com
62 Alexander Drive			...!mcnc!rti!xyzzy!goudreau
Research Triangle Park, NC  27709, USA