User`s guide

Dialing translations 17-45
Identifying translation table requirements
Standard 1.0 System Administration Guide January 1998
Identifying translation table requirements
Introduction
Not all systems require translation tables, so you must first
identify if there is a need for a table on your system.
If the following cases are the only local and long distance
scenarios that take place, you will not have to create any
translation tables. Meridian Mail will use the prefixes that are
defined in the Dialing Translation Defaults screen to perform all
the translations required.
Normal dialing cases
All DNs with the same area/city code as the local site are treated
as local calls.
All DNs with a different area/city code to the local site, are
treated as long-distance.
Meridian Mail assumes that all the numbers in the local area/
city code are dialed with the local dialing prefix and without the
local area/city code (in other words, with a format such as
9-xxx-xxxx).
Meridian Mail also assumes that all numbers in area/cities other
than the local area/city are dialed with the long distance dialing
prefix and with the area/city code of the number (in other
words, with a format such as 6 [xxx]-xxx-xxxx).
If these two statements are true for your system, you do not
need to define any translation tables. Otherwise, if either or both
of these statements are not always true for your system, then
translation tables will have to be defined for the exceptional
cases.