Avaya CallPilot Message Networking Manuel d'utilisateur télécharger pdf (Page 34)

Chapter 4 Setting up AMIS

P0919429 06

Examples of Dialing Translation Tables

The following tables are examples of Dialing Translation Tables and how they work. Every

Dialing Translation Table entry consists of an Input value column and an Output value column.

The values in the Input column represent the leading digits of the Network extensions which, if

matched, are replaced by the corresponding value in the Output column. The * after a value

signifies any digits in the telephone number that remain to be dialed. CallPilot automatically adds

the * after every Input and Output value.

A telephone number either matches or does not match a specific Input value.

A Dialing Translation Table from a site in metropolitan Toronto

A Dialing Translation Table from a site in Mountainview, California

INPUT OUTPUT Explanation

011* 011* The Table does not attempt to translate international telephone numbers.

416* * The Table removes the 416 area code and dials all calls as 7 digits.

905206*

90527*

etc.

(135 more

entries)

905206*

90527*

etc.

(135 more

entries)

These telephone exchanges can be dialed as local (no long distance charges)

10 digit calls from the 416 area.

905* 1905* All other 905 numbers not listed in the Input column above are long distance

numbers and must be dialed as 11 digit long distance numbers.

* 1* Any numbers that start with digits other than 011, 416 and 905 are long

distance, and have 1 added as a prefix.

INPUT OUTPUT Explanation

The Dialing Translation Table is empty. The local network in

Mountainview supports 10 digit national dialing with recognized long

distance charging.

In situations like the Mountainview example, there is no need to build a

Dialing Translation Table.

1 2 ... 29 30 31 32 33 34 35 36 37 38 39 ... 73 74

Pas de commentaire

Avaya CallPilot Message Networking Manuel d'utilisateur Page 34