Dial Plan Tables - 3Com NBX 100 Installation Manual

50 C 2: C
HAPTER ONFIGURING THE

Dial Plan Tables

D P
IAL LAN
Dial Plan tables contain information that controls how the NBX 100
routes calls. Each dial plan configuration file consists of at least three Dial
Plan tables:
Internal (must be table ID 1)
I
Incoming (must be table ID 2)
I
Least Cost Routing (must be table ID 3)
I
Tables 1, 2, and 3 must exist. Do not delete them. You can create
additional Dial Plan tables if necessary, but they must be numbered 4 or
higher.
If the client is sharing the NBX 100 with another company and wants to
control calls differently, you can add a fourth table.
Example: You assign one extension range to Company A and a different
range to Company B. The fourth table controls the extension range for
Company B, so that outbound calls from Company B's extensions use
only their external telephone lines.
You might also need a fourth table if a single company had two sites but
only one NBX 100. In order to properly route emergency (911) calls, you
would need a fourth table to define which extensions used each
dedicated 911 telephone line.
Example: Users at site A dial 911 and the NBX 100 uses the Internal table
(table ID 1) to make the emergency call on one external telephone line.
Users at site B dial 911 and the NBX 100 uses table ID 4 to make the
emergency call on a different external telephone line. The emergency
services people know, based on the dialing number, which site has the
emergency.
Enhanced 911, known as E911, is available in some areas. This enables
the emergency services people to identify the specific location of the
emergency site. For example, in a campus of several buildings, the
emergency response people could identify the specific building, floor, and
location from which the emergency call originated. The NBX 100
supports E911 over ISDN. The user must define an outbound call
Pretranslator to provide the specific extension number from which the
911 call originated.