User`s guide

17-12 Dialing translations
Translation tables
Standard 1.0 System Administration Guide January 1998
Translation tables
Concept
Translation tables are the second level of the translation
process, after the dialing translation defaults.
These tables handle certain dialing exceptions that may not
arise in your system. Therefore, translation tables will not be
required by all systems.
For example, in a normal local dialing scenario, the area/city
code (in North America, it is called the Numbering Plan Area or
NPA) of the calling site is the same as the called site. A call in
this situation would be handled by the dialing defaults.
However, there may be a dialing scenario where the area/city
codes are different but the call is still considered local. A
translation table would have to handle this case in order to
determine that the call in question could be handled as local
rather than as long distance.
The exceptional cases that require translation tables are outlined
in “When translation tables are required” on page 17-14.
Restriction/
permission lists
Meridian Mail applies translation tables before checking
restriction/permission lists.
Example
For example, a call to another area/city code is considered local,
and the restriction/permission list applied to a Fax on Demand
application allows only local calls.
If a translation table is not set up for this exceptional dialing
scenario, the system will assume that the callback number is
long distance (because the area/city code is different from the
local site) and Meridian Mail will not deliver the fax (since the
restriction/permission list does not allow delivery to long
distance numbers).