January 1999 Headlines

wpe18.jpg (915 bytes) requires to be viewed (Acrobat is Free)

ballgreen.gif (941 bytes) Jan 4: CA: GTE & PacBell Refuse To Participate In Number Pooling Trial
ballgreen.gif (941 bytes) Jan 4: MISC: FCC Requests Inquiry Into 500 & 900 Number Portability
ballgreen.gif (941 bytes) Jan 5: IL: Evolving Systems Helps Providers Continue Number Pooling Tests
ballgreen.gif (941 bytes) Jan 5: MO: 636 Selected For Latest 314 Split
ballgreen.gif (941 bytes) Jan 6: MO: 636 To Relieve 314 Crunch
ballgreen.gif (941 bytes) Jan 6: CA: 323 Area Code Becomes Mandatory On Saturday, Jan 16
ballgreen.gif (941 bytes) Jan 6: MN: 651 Area Code Becomes Mandatory On Sunday, Jan 10
ballgreen.gif (941 bytes) Jan 6: AZ: 623 Selected For West Valley Split
ballgreen.gif (941 bytes) Jan 6: FL: 407 To Get Split & Extended Overlay; 321 Recommended Relief Code
ballgreen.gif (941 bytes) Jan 7: ON: 647 Assigned As Canada's First Overlay In Toronto's 416 Area
wpe18.jpg (915 bytes) Jan 8: NANPA PL: AB: 780/403 NXX List & Test Numbers
ballgreen.gif (941 bytes) Jan 8: MA: No Popular Choices In Eastern Mass Area Code Shuffle
ballgreen.gif (941 bytes) Jan 8: MISC: NANPA Releases 1999 COC Transition Schedule
ballgreen.gif (941 bytes) Jan 8: CA: Public Meetings Set For 760 Area Code Relief
ballgreen.gif (941 bytes) Jan 11: IL: Transaction Network Services Prepares For Number Pooling
ballgreen.gif (941 bytes) Jan 11: MISC: Y2K Only The Beginning; NANP Running Out of Numbers
                                    (Originally Published October 12, 1998)
ballgreen.gif (941 bytes) Jan 14: CA: iPrint.com To Provide Cost Relief As Area Codes Change
ballgreen.gif (941 bytes) Jan 14: TX: New 361 Area Code Calls Up Complaints
ballgreen.gif (941 bytes) Jan 15: CA: 323 Area Code Becomes Mandatory Today
ballgreen.gif (941 bytes) Jan 16: TX: Houston Area Code 832 And Mandatory 10-D Dialing Begins Today
ballgreen.gif (941 bytes) Jan 16: TX: Information About Dallas And Houston Area Code Overlays
ballgreen.gif (941 bytes) Jan 16: AB: They're Taking Our 403 From Us (Originally Published November 30, 1998)
ballgreen.gif (941 bytes) Jan 16: PQ: Automatic Routing To 450 Area Code Ends
ballgreen.gif (941 bytes) Jan 17: MISC: By The Numbers - Area Codes Are Disappearing Regional Identities
ballgreen.gif (941 bytes) Jan 17: NANPA: December Report On Relief Activities
ballgreen.gif (941 bytes) Jan 18: New England: ME & NH Recommend Overlay; MA Still Can't Decide What To Do
ballgreen.gif (941 bytes) Jan 18: CA: 323 Dialing Now Required
ballgreen.gif (941 bytes) Jan 18: MO: Businesses Need To Brace For New 636 Area Code
ballgreen.gif (941 bytes) Jan 19: KY: 270 Area Code Brings Number Of Problems (Originally Published November 18, 1998)
ballgreen.gif (941 bytes) Jan 19: IL: Ameritech To Offer InterLATA Simplified Dialing For Businesses
ballgreen.gif (941 bytes) Jan 25: IL: Ameritech Offers Island In Area Code Flood
ballgreen.gif (941 bytes) Jan 25: AB: Norther Half Of Province Gets 780 Area Code Today
ballgreen.gif (941 bytes) Jan 25: MA: State Hopes To Curb New Area Code Splits
ballgreen.gif (941 bytes) Jan 25: MA: Area Code Angst
wpe18.jpg (915 bytes) Jan 25: NANPA PL: CA: 669 To Overlay 408 Area Code
ballgreen.gif (941 bytes) Jan 27: MO: PSC Sets Timetable For 636 Area Code Schedule
ballgreen.gif (941 bytes) Jan 27: CA: 530 & 626 Area Code Relief Meetings To Be Scheduled
ballgreen.gif (941 bytes) Jan 27: AB: Province Gets New 780 Area Code
ballgreen.gif (941 bytes) Jan 27: FL: 727 Area Code Becomes Mandatory On February 1
ballgreen.gif (941 bytes) Jan 27: NY: PSC Recommends 516 Overlay, With County-Line Split Alternative
ballgreen.gif (941 bytes) Jan 28: MO: Recommendations For 636 Introduction To Be Considered By PSC
ballgreen.gif (941 bytes) Jan 29: MO: 636 Scheduled To Start In May; Permissive Until February, 2000

 

NOTICE TO ALL PARTIES: This is a FREE ACCESS site. No profit is derived from this contents or articles displayed herein. Selected materials contained herein may be copyrighted by their respective owners and are presented herein for research and/or reporting purposes only pursuant to Article 17, Section 107 of the United States code dealing with copyright law. Anyone with questions concerning content should direct them to the site administrator. Likewise, we do not warrant the accuracy, reliability, or timeliness of any information in this public access system, and shall not be liable for any losses caused by such reliance on the accuracy, reliability, or timeliness of such information. Portions of such information may be incorrect or not current. Any person who relies on any information obtained from this system does so at his or her own risk.