Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!netsys!vector!nobody From: cmoore@BRL.MIL (VLD/VMB) Newsgroups: comp.dcom.telecom Subject: numbers in use but not recognized yet Message-ID: Date: 3 Feb 89 15:36:13 GMT Sender: chip@vector.UUCP Lines: 11 Approved: telecom-request@vector.uucp X-Submissions-To: telecom@bu-cs.bu.edu X-Administrivia-To: telecom-request@vector.uucp X-TELECOM-Digest: volume 9, issue 48, message 1 A reader previously wrote of being in a new area code (508 in Massachusetts) and learning that some people in distant areas could not yet call 508 area. This apparently also happens with prefixes. Once in Maryland before 0+number went away, I attempted to dial 0-850-xxxx and it got rejected; 850 was a rather new prefix in the Baltimore-Washington Int'l airport area. And someone else in Maryland could not call 202-994 prefix (long-distance, to DC). (I.e. both calls required help from a human operator.) Was there a similar experience with people on N0X/N1X prefixes? (I.e. some people in distant areas had calls to such prefixes rejected by their local equipment?)