Figure 71 Using destination codes to access another system
Deciding on a code
Note: When configuring a private network, ensure the numbering plan
does not conflict with the public telephone network. For example, in
North America, using "1" as an access code in a private network,
conflicts with the PSTN numbering plan for long-distance calls
When deciding on which digits to use to start your destination codes, consider the following:
•
Ensure that the digit or digits you want to start your destination codes with do not match any of
the access codes, including the line pool codes that already exist in your system.
You may find that you need to delete line pool codes and create a route and destination code
instead. This could occur if you want to set up fallback to a public line, for instance. If the
public line is accessed by a line pool code, you would have to change access to a route so you
could create a fallback schedule with the destination code used for the primary line (or lines, if
you have more than one outgoing line pool that requires fallback).
•
Decide how much of the common part of a dial string you want your users to have to dial, and
how much you can put in the dial string.
•
If you want specific dial strings to use specific routes, map these out first.
For instance, if you want users to dial between BCMs over VoIP lines, you create destination
codes specific to those systems that use the VoIP line pool, using the digits with which the
users are familiar. You can then create a unique destination code for the call you want to route.
Chapter 24 Dialing plans
Networking Configuration Guide
241