User`s guide

Dialing translations 17-55
Local dialing to a different area/city code (area/city code required)
Standard 1.0 System Administration Guide January 1998
Translation table
setup (version 2)
You could also define the translation in the inverse manner
from version 1. That is, you could define the exchange codes
that require the long distance prefix, while the remaining
exchange codes would be assigned the local prefix by default.
Screen (version 2)
The following screen illustrates the version 2 translation table.
Logic of version 2
The exchange codes that are long distance within the 905 area/
city code are explicitly defined in the table instead of the local
codes. (Note that the two prefixes for exchange codes in the
table and exchange codes not in the table fields are reversed
from version 1).
Hint for planning
translation tables
The way in which you define the table will depend on how
many exchange codes within the area/city code are considered
local and how many are considered long distance. If, for
example, 100 exchange codes in the 905 area/city code are long
distance and ten are local, the version 1 translation table would
be easier to create since you would have to define only ten
codes. However, if there were more local exchange codes than
long distance codes, you would create a table similar to that in
version 2.