more topics
|
Uniform Dial Plan Features
Intersystem Calling
In a private network, users on one local system can call extensions on other
systems in the network. They dial these extensions as inside calls. This topic
describes how to set your system up so that local users can reach these non-local
dial plan extensions. It also describes how users dial non-local extensions.
Extension Ranges
When local users call other users on a remote private-networked system, the
local System Manager programs the ranges of extensions of the remote system
into a non-local dial plan.
Each switch in the private network has both a local dial plan and a non-local
dial plan that together form the UDP. The local dial plan is set up at the local
system by using System Renumbering. The non-local dial plan is a list of up
to 50 different extension number ranges for other systems in the private network.
When users call one another, the system searches the local dial plan; if the
extension number is not found, it consults the non-local dial plan and associated
routing information in order to send the call directly or indirectly to another
system in the network. Routing information is programmed into as many as 20
patterns consisting of routes. Routes specify digit manipulation, pools, voice/data
call type, and FRLs similar to those used for ARS.
 |
A reference list is programmed on the local system to find non-local
extensions and direct calls to them.
|
When you specify a non-local extension range, the system verifies that extension
numbers on the local system do not conflict with those programmed on a networked
switch. For example, if Extension 110 exists in the local system, Extension
1100 cannot be included in the extension range for a non-local networked system.
The local system also checks to see whether new extension number ranges conflict
with existing ranges programmed for non-local systems.
| |
The Non-Local UDP Administration Form in the Installation Specification
should be kept accessible for programming. Contact your Avaya representative
for a generated copy for your network.
|
When setting up your network for intersystem calling, keep the following important
points in mind:
- You cannot program the local ARS access code or pool dial-out codes into
non-local dial plan extension ranges; the system blocks this programming.
Non-local extension range numbers cannot begin with the local ARS access code.
If, for example, the ARS access code begins with 9 and a non-local dial plan
extension range is 9230-9330, programming is blocked. You must not program
the ARS access code of a non-local system into the non-local dial plan because
it poses a security risk; it is best if all networked systems assign the same
ARS access code.
- The Remote Access codes of non-local systems can be included in the non-local
dial plan for the convenience of technicians providing technical support or
for users to program their forwarding home extensions on a non-local system.
Each system should use a unique and unambiguous Remote Access code.
- Your non-local dial plan programming has no effect on the remote system
or systems it references. Local dial plan changes made at a system do not
automatically update the non-local dial plan numbering plans of networked
systems. To avoid misrouting, it is recommended that manual adjustments to
the non-local dial plans made by network System Managers be made at the same
time. System Managers should provide ranges wide enough to avoid problems
for future non-local dial plan changes.
- In most cases, the extension numbers programmed into the non-local dial
plan should be the same extension numbers that users at remote systems dial
to reach one another within their systems. The main exception occurs when
non-local dial plan numbers refer to extensions on DEFINITY ECS, DEFINITY
BCS, or DEFINITY ProLogix Solutions systems, which include five digits.
- Extensions included in ranges must be unique and unambiguous across systems.
In other words, if the local system includes extension 112, that system blocks
the programming of a non-local extension range that encompasses extension
1122. If it allowed the range, calls to 1122 would be misrouted because the
system would send calls for extension 1122 to extension 112 as soon as it
received the first three numbers. In this example, the local system prevents
the numbering conflict. If the local system is connected to more than one
other networked system, however, programmed extension ranges must assure proper
routing. For example, if the manager on System A must program extension ranges
on two connected systems, System B and C, the specified ranges on Systems
B and C must be unique and unambiguous. If System B includes the range 2030-2049,
System C cannot include an extension range that encompasses either extension
203 or extension 204.
- MERLIN MAGIX Integrated System dial plans may include 2-digit, 3-digit,
or 4-digit extension numbers. However, DEFINITY ECS, DEFINITY BCS, or DEFINITY
ProLogix Solutions users must dial four digits in order to reach a MERLIN
MAGIX Integrated System extension in a network. Although the MERLIN MAGIX
Integrated System can be programmed to drop digit or digits, use 4-digit dial
plans in networks with DEFINITY ECS, DEFINITY BCS, or DEFINITY ProLogix Solutions.
- When planning non-local extension ranges, PRI dial plan routing and DID
numbers must be considered. If calls are routed across the network to these
numbers, they also must not conflict with extension ranges in other network
systems. In addition, UDP routes must specify correct digit manipulation (deleting
or adding digits). When such calls are routed to 5-digit DEFINITY ECS, DEFINITY
BCS, or DEFINITY ProLogix Solutions systems, special considerations apply.
MERLIN MAGIX Integrated System non-local dial plan numbering specifies extensions
up to four digits long, while DEFINITY ECS, DEFINITY BCS, or DEFINITY ProLogix
Solutions systems may have 5-digit extension numbers. There are two methods
you can use to number DEFINITY ECS, DEFINITY BCS, or DEFINITY ProLogix Solutions
non-local dial plan ranges to match the five digits.
Choose one of the following techniques, depending upon the actual extension
numbers you are entering in ranges and potential conflicts:
- Specify ranges in MERLIN MAGIX that include the first four digits in the
extension numbers. Each number you enter in the range represents 10 numbers
in the remote 5-digit system. For example, an extension range entered as 4321
through 4322 represents remote extensions 43210 through 43229. Users actually
dial five digits. The local system recognizes the number range by the first
four digits, but sends all five digits to the DEFINITY ECS, DEFINITY BCS,
or DEFINITY ProLogix Solutions system.
- Enter the last four digits and use UDP routing to prepend the first digit
in the DEFINITY ECS, DEFINITY BCS, or DEFINITY ProLogix Solutions extension
number. The local system recognizes the number range using the last four digits.
Users dial only the last four digits. If DID calls must reach 5-digit DEFINITY
ECS, DEFINITY BCS, or DEFINITY ProLogix Solutions extensions from a MERLIN
MAGIX Integrated System, this method of routing should be used. However, DID
facilities should be connected directly to the local DEFINITY ECS, DEFINITY
BCS, or DEFINITY ProLogix Solutions systems.
