Nortel BCM 3.7, Manual

Page: 341 / 1004

Grouping destination codes using a wild card 341
Programming Operations Guide
economical route is being used. Depending on how many exceptions there are, you can use the
wild card at the end of the string to save yourself from the necessity of entering a number of
destination codes with the same leading digits. Refer to
“Grouping destination codes using a
wild card” on page 341 .
• If you are setting up a new system where users do not have previously-established dialing
patterns, you can use simpler destination codes. For example: You can establish 9 as the
destination code for dialing outside the system, 5 for dialing any calls within networks on the
local exchange, and 7 for dialing any calls within the network to destinations outside the local
exchange.
Therefore:
System A calling to the public network would dial 9XXXXXXX or 91XXXXXXX if the call
is long distance.
System A calling to System B, which is in the same city, would dial 5XXXX
System A calling to System C, which is in another exchange area, would dial 7XXXXXXX
Note: If the network is using CDP for the dialing plan, the destination codes could be the
leading digit of the DN code, since that needs to be unique for each system. However, this
would depend on which digits have already been taken by other coding in the system.
Grouping destination codes using a wild card
If you have a number of destinations that have the same route and digit absorb length, you can
group these codes under one destination code to maximize your destination code table. In this case,
the start digits will be the same, but the last character will be the wild card, and indicates any digit
between 0 and 9. However, if there is a conflict with other digits already programmed or used by
other destination codes, an error message appears.
For instance, you might use the same route (555) to a number of remote sites. Each site is accessed
with the same external # (dial out string), except for the last digit, which is unique to each site.
The exception to this is a site with a totally different access number and line pool requirement
(route 565). This example is shown in the following table.
If you do not use wild cards, you would need to create a separate Destination code for each unique
dialout, as shown in the following table.
Table 64 Establishing routes and dialout requirements
Route Dial Out (external #) Line Pool
555 0162 237 625<unique number from 0 to 9> Line Pool C
565 0173 133 2211 Line Pool A
Table 65 Destination codes not using a wild card
Destination codes Route Absorb Length Dial Out
0621 555 3 0162 237 6251
0622 555 3 0162 237 6252