Nortel BCM 3.7, Manual

Page: 338 / 1004

338 Using destination codes
N0008589 3.3
Using destination codes
Destination codes allow you to control how the system interprets and routes dial strings from
internal sources. Destination codes are similar to line pool codes except that by using routes
(which attach dial strings and DN type designators to line pools) and schedules you can control
what digits the user has to dial and how the system routes the call out of the system, including what
numbers from the dial string get added or deleted to the route dialout.
The numbers used for destination codes must not conflict with the following:
You can enter destination codes to a maximum of 12 digits.
This section includes the following information:
• “Why use destination codes?” on page 339
• “Deciding on a code” on page 340
• “Grouping destination codes using a wild card” on page 341
• “Configuring destination codes with wild cards” on page 342
• “Setting up a destination for local calling” on page 344
• “Setting up a route through a dedicated trunk” on page 345
• “Adding Carrier access codes to destination codes” on page 346
• “Programming for least-cost routing” on page 347
• “Using multiple routes and overflow routing” on page 348
• “Using dialing restrictions with routing” on page 350
Table 63 Destination codes: avoiding numbering conflicts
XXXX Numbering cannot conflict with these features
First digit must not conflict with: Entire code must not conflict with:
Park
prefix External
code
Direct
dial
digit
Auto
DN DISA
DN
Private
access
code
Line pool
codes Telephone
DN
Other
destination
codes
Public
target line
recv’d
digits
Destination
code XXXX * XXXX XXXX XXX XXX XXXX XXXX XXXX XXXX