Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!BRL.ARPA!cmoore
From: cmoore@BRL.ARPA (Carl Moore, VLD/VMB)
Newsgroups: mod.telecom
Subject: N0X/N1X impact on dialing
Message-ID: <8610192305.AA17513@ucbvax.Berkeley.EDU>
Date: Fri, 3-Oct-86 14:40:41 EDT
Article-I.D.: ucbvax.8610192305.AA17513
Posted: Fri Oct  3 14:40:41 1986
Date-Received: Mon, 20-Oct-86 00:48:20 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13
Approved: telecom@xx.lcs.mit.edu

I have just seen N0X/N1X in use in 214 area (includes Dallas, TX, in the
same state where 713 split without going to N0X/N1X?).  The phone book says
to use areacode 214 for direct-dial long-distance calls within that area.
Since the Dallas & suburban N0X/N1X points I saw are not far from the
817 areacode boundary, it's necessary to check for their being local to
points in 817 area!  (It turns out that 2 of those N0X/N1X prefixes do
have local service into 817 area, which, like 214, requires area code for
direct-dial long distance calls within itself.)

New Jersey 201 area also has N0X/N1X, and it and 609 both now require 1+ on
direct-dial out-of-area calls (but what about those out-of-area calls which
were local earlier--i.e., you could dial them AND all points in your N.J.
area code with just the 7-digit local number).