Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!nucsrl!telecom-request From: davidb@pacer.uucp (David Barts) Newsgroups: comp.dcom.telecom Subject: 1+206 Dialling Coming to Washington Message-ID: Date: 19 Feb 91 17:11:07 GMT Sender: news@casbah.acns.nwu.edu Organization: TELECOM Digest Lines: 26 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 11, Issue 132, Message 4 of 9 Originator: telecom@delta.eecs.nwu.edu Several months ago (or was it that long) there was a discussion in this Digest about NPA 206 (western Washington state) running out of NXX exchange codes, and the fact that we will soon be seeing N0X/N1X exchange codes. Well, on the news this morning it was reported that beginning this November, a permissive period will begin when intra-NPA LD calls can be dialed as 1+206+7D or the existing 1+7D. Sometime later, 1+206+7D dialling will become mandatory (they didn't say when). So common sense has prevailed (this time), and there is no longer any need for us in NPA 206 to have to worry about accidentally dialling a seven-digit long distance call. Our Usenet feed has been very unreliable recently, and I have missed the past few days' worth of comp.dcom.telecom. My apologies if this item has been posted already. Also, there has been a flurry of recent activity in the Washington Utilities and Transportation Commission and the State Legislature about US West's Caller*ID proposals for our state. If nobody else has posted anything, I'll post a short summary of the situatiuon so far. David Barts Pacer Corporation, Bothell, WA davidb@pacer.uucp ...!uunet!pilchuck!pacer!davidb