Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!killer!vector!telecom-request From: David_W_Tamkin@cup.portal.com Newsgroups: comp.dcom.telecom Subject: recording from another area code/long-distance call to ANAC Message-ID: Date: 24 Aug 88 21:55:31 GMT Sender: chip@vector.UUCP Lines: 52 Approved: telecom-request@vector.uucp (USENET Telecom Moderator) X-TELECOM-Digest: volume 8, issue 134, message 3 X-Submissions-To: telecom@xx.lcs.mit.edu (Mailing List Coordinator) X-Administrivia-To: telecom-request@vector.uucp (USENET Telecom Moderator) Lars Poulsen, in Digest v8, #122, reported the following when he tried calling my local ANAC code from his location: ------------------------------ I tried this, from my GTE line (805) 682-xxxx (Santa Barbara, CA). 290 yields (ring, ring, redirect, recording:) "We're sorry ... cannot be completed". 1-312-290-1234 yields (redirect, recording:) "Your call cannot be completed ... 818-4T". Since 290 does not require 7 digits before the rejection from the local switch, it seems like this prefix gets special handling (or is that true of unassigned prefixes in general ? The long distance call get rejected in the LATA router. Wouldn't it be nifty if it had gone thru ?. / Lars Poulsen ------------------------------ Dave Cantor got a similar recording from an intermediate area code when he tried calling Weathertrak in New York from New Hampshire, as he said in Digest v8, #128: ------------------------------ When I dialed it directly (1-212-540-3000) I got rejection messages from US Sprint, from MCI, and from AT&T indicating they could not complete the call. The AT&T message was "Your call cannot be completed as dialed. 508-2T." Funny, I was calling from a New Hampshire telephone (NPA 603), but got an area 508 message! [ ... ] One question: Why would I get a message from 508-2T when dialing from an area 603 telephone? ------------------------------ ====== Since 290 [Centel's three-digit ANAC] is not a valid prefix in area code 312, Lars's long-distance company couldn't find it in its database. Surely Centel's ANAC facility here couldn't be expected to report the number from which it received a long-distance call! Patrick Townson cannot even call it from his location in Illinois Bell's part of area code 312. Both in his case of calling an invalid prefix in 312 from 805 and in Dave's case of dialing a restricted prefix in 212 from 603, the rejection message came from a third area code. I imagine that Lars's call got routed as far as area code 818 (a bit out of the way geographically but not unreasonably so) and Dave's call as far as 508 (not out of the way at all) because their long-distance providers had their switching centers and databases of reachable prefixes in those locations. Lars's call to a nonexistent prefix in 312 was rejected by a machine sitting in area code 818 and Dave's call to a restricted prefix in 212 was rejected by a machine sitting in area code 508, so those were the area codes in the announcements. David_W_Tamkin@cup.portal.com