Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request From: cmoore@brl.mil (VLD/VMB) Newsgroups: comp.dcom.telecom Subject: Re: 215 Area Code Loses "1" per Newspaper 'Reporter' Message-ID: <15637@accuvax.nwu.edu> Date: 22 Dec 90 17:08:53 GMT Sender: news@accuvax.nwu.edu Organization: TELECOM Digest Lines: 38 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 901, Message 4 of 12 Replying to Steve Schallehn : The instructions vary if you make a local call which crosses an area code boundary. You wrote about the Kansas City area. In the Washington DC area, prefixes had to be unique for the entire area; when prefixes started running short in that area, they were generalized from NNX to NXX, and when they ran short again, the local calling instructions were changed to require the area code (without leading 1) for a local call crossing an area code boundary. Also, Kansas and Missouri each have more than one area code. 1 + 7D there should only work within your own area code (in Kansas City, the area codes are 816 and 913). Replying to David Cornutt : The leading 1's meaning "what follows is an area code" makes N0X/N1X numbers (not NNX numbers, which were already available) useable as exchange numbers; in other words, the exchange numbers generalized from NNX to NXX. Yes (from other sources in this Digest), area codes of the form N0X/N1X are projected to run out circa 1995, and then area codes will have to generalize to NXX. Replying to Lyle A. McGeoch : The calling instructions you cite for northern New Jersey (201 and 908) were also put into effect in 609; a message to me on this matter cited statewide uniformity, and there later appeared a special case where local service from Barnegat (609 area) includes two N0X prefixes in Toms River (201, to become 908), with local calls from 609 area to other areas still being seven digits, at least then. Replying to Michael Scott Baldwin : No, in New Jersey you did not force 1 for long distance calls. You forced 1 in front of an area code (we're not talking about 0+ calls). Long distance within your own area code in New Jersey is just 7D, not affected by the use of N0X/N1X prefixes.