Table of Contents
Advertisement
340
Using destination codes
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 digit(s) to use to start your destination code(s), you need to take into
consideration:
•
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).
•
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 Business Communications Managers over VoIP
lines, you would create destination codes specific to those systems which 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 over the land line.
Example: If users are used to dialing 9-1-555-555-<DN number> to reach another system
(whose DN codes start with 6), you create a destination code of 915555556A, using the VoIP
line pools (users dial the destination code plus the DN of the telephone they want to reach on
the other system). The letter A at the end of the code represents any number from 0 to 9 which
is not used by any other destination code.
If you need to use land lines for a specific connection on the other system, you can create a
destination code specific to that destination number and attach it to the route set up with the
landline line pool (i.e. 915555556333, 6333 being the DN of the device on the other system.
When the user dials that specific number, the call will always go over the land line). Note that
by entering this code, users dialing with the code in the previous paragraph could never dial
any DN that started with 63XX.
•
If you want to use VoIP lines as your main lines, but you want to program one or more land
lines as fallback lines, you need to configure the routing and routing schedules so that the user
dials the same number, regardless of which routes get used. You use the external # dialout
string and absorb digits fields under the schedules in Destination code programming for this
purpose.
•
If a company wants to use VoIP lines between sites for interoffice calls, but not necessarily for
all the voice traffic, they can configure specific destination codes for the VoIP routes. In this
case, the destination code contains the same digits as a user would dial for a landline, thus,
making the shift transparent to the user and, at the same time, ensuring that the most
N0008589 3.3
Advertisement
Table of Contents
