I work for a large nationwide company which has PBX's in several hundred US cities. My problem has to do with the task of administering local dialing rules in the individual PBX's. For example, in Miami (305) all local calls are 10D (NPA 305, 786, and part of 954) However, a portion of NPA 954 is toll and requires a '1'. Does anyone know of a searchable data_base_ which indicates a 'local' or 'toll' call from a particular NPA-NXX? I tried checking out the Bell South web site to see if they would show what is a local and toll call out of Miami- but no luck! The local phone directory has it but it is outdated before it hits the street.

writes: I work for a large nationwide company which has PBX's in several hundred US cities. My problem has to do with the task of administering local dialing rules in the individual PBX's. For example, in Miami (305) all local calls are 10D (NPA 305, 786, and part of 954) However, a portion of NPA 954 is toll and requires a '1'. Does anyone know of a searchable data_base_ which indicates a 'local' or 'toll' call from a particular NPA-NXX? I tried checking out the Bell South web site to see if they would show what is a local and toll call out of Miami- but no luck! The local phone directory has it but it is outdated before it hits the street. What you need is called a LERG - Local Exchange Rate Guide - I believe you can subscribe to the thing, possibly from Lockheed Martin.  Yes, you would need to subscribe so as to avail yourself to the many changes as they occur. Actually, no.  The LERG (Local Exchange Routing Guide) does *NOT* contain this data, besides costing rather a lot of money. The LERG will tell you what rate center, switch, operating company, LATA, and billing coordinates apply to each prefix, and some other information relating to routing the call within the network, but it DOES NOT tell you which prefixes are local to which other prefixes, nor does it tell you how a subscriber should dial a given number from a given location.  All that it will tell you is that, for instance, 954-227 is an ordinary prefix in Coral Springs, Florida, served by the switch PMBHFLCSDS0, which is a 5E, operating company #9417, LATA #460, sub-LATA #17, at billing coordinates 08267 vertical, 00591 horizontal, and it does offer Local Number Portability, plus a few other bits and bobs of routing information. However, if you can get a listing of all RATE CENTERS that are local to you, you can use the LERG's cheaper cousin, the NNACL (NPA-NXX Active Code List), updated with the monthly NNAG (NPA-NXX Activity Guide), to keep a current list of which prefixes are associated with those rate centers.  You still have to get the list of local-call rate centers from your local exchange carrier or from the tariffs.  However, if you can write your own _script_ to integrate the NNAG into the NNACL, you can keep yourself up-to-date permanently for a one-time $150 cost. You can also subscribe to services that maintain data_base_s of which prefixes are local to which other prefixes, but that costs rather a lot of money, also. The LERG and NNACL can be purchased from Telcordia (formerly Bellcore) Traffic Routing Administration, <http://www.trainfo.com.  The NNAG, which is a monthly update to the NNACL, is a free download at the same web site. Incidentally, Miami may be local to all of 786, but part of 305 is definitely not local.  You have to dial 1+ if you call Key West, for example.  (786 is almost exactly Miami/Dade County, but 305 includes the Keys as well.)

Jim Sielaff wrote in message < This e-mail address is being protected from spam bots, you need JavaScript enabled to view it Does anyone know of a searchable data_base_ which indicates a 'local' or 'toll' call from a particular NPA-NXX? Try http://www.nanpa.com/ which is the North American Dialing Plan. Good Luck! No, NANPA doesn't know or care about local/toll status.  It just assigns the area codes, and now in many states the prefixes.  It has neither control of nor knowledge of rate plans and such. The answer, as previously posted, is to get a list of the rate centers that are a local call from each location, and then use information available for a reasonable cost from Telcordia (formerly Bellcore) that will tell you all the prefixes assigned to each rate center.

However, if you can get a listing of all RATE CENTERS that are local to you, you can use the LERG's cheaper cousin, the NNACL (NPA-NXX Active Code List), updated with the monthly NNAG (NPA-NXX Activity Guide), to keep a current list of which prefixes are associated with those rate centers.  You still have to get the list of local-call rate centers from your local exchange carrier or from the tariffs.  However, if you can write your own _script_ to integrate the NNAG into the NNACL, you can keep yourself up-to-date permanently for a one-time $150 cost. Actually, I should add some caveats here.  For example, in the Dallas/ Fort Worth area, you have absolutely no way of knowing what prefixes are local or toll except demanding that your local telco give you periodic updates. The reason is that, within a given rate center, some prefixes are ordinary while others may be Metro prefixes.  There is nothing in the LERG or NNACL or NNAG data that distinguishes them, but there are many cases where ordinary prefixes in a given rate center are toll (and require 1+) while Metro prefixes in the same rate center are local (and must NOT be dialed with 1+).  For example, Dallas to Fort Worth.