Configuring destination codes with wild cards
347
Programming Operations Guide
Follow these steps to program a long distance carrier access code into a destination code.
1
Create a route that uses a line pool containing local lines only.
2
Program the route to use a line pool containing the lines used to access the long distance
carriers.
3
Type the dialout digits, which are the same as the access digits. For example, if the access code
is 10222, the dialout digits are 10222.
4
Create a destination code 91: 9 (for outside access) and 1 (for long distance). You must use a
valid destination code. Refer to
“Using destination codes” on page 338
.
5
Set
Absorbed Length
to 1.
The digit 9 is only used internally and should be dropped. The 1 is needed to direct the call to
the public carrier network.
TIPS:
The destination codes 9 and 91 used in the examples cannot be used together. If you need
the destination code 91 to direct long distance calls, you must create a separate set of codes that
use local calling routes. These codes would be, for example, 90, 92, 93, 94, 95, 96, 97, 98 and 99.
Refer to
“Grouping destination codes using a wild card” on page 341
for information on
programming destination codes.
Programming for least-cost routing
It can be less expensive to use another long distance carrier at a different time of day. Continuing
with the example used in the previous flowchart, the lines that supply local service in normal mode
are also used for long distance service after 6 p.m. because that is when rates become competitive.
For the system to do this automatically, you must build another route.
Follow these steps to build a route for a secondary carrier:
1
Beside
Route:
enter an available route number.
2
Choose
No number
for the dialout.
3
Choose the line pool that contains the local service carrier lines.
4
Now you need to create a destination code and assign the route to the Night schedule.
In this case, the change in route uses the start and stop times for Night Schedule.
5
Add 91 as a
Destination code
.
6
Make sure
Absorbed length
is set at 1.
7
Under
Night schedule:
enter the route you defined in step 1.
Calls that begin with the digits 91 travel out without using the access code when the Night
schedule becomes active or when you turn it on at a control telephone.
Summary of Contents for BCM 3.7
Page 4: ...4 Software licensing N0008589 3 3...
Page 32: ...32 Contents N0008589 3 3 W 937 Index 939...
Page 46: ...46 Tables N0008589 3 3...
Page 64: ...64 How to get help N0008589 3 3...
Page 90: ...90 Manually activating Telnet N0008589 3 3...
Page 116: ...116 Delayed system restart N0008589 3 3...
Page 194: ...194 Configuring a data module N0008589 3 3...
Page 276: ...276 Setting line telco features N0008589 3 3...
Page 310: ...310 Using COS passwords N0008589 3 3...
Page 364: ...364 Enhanced 911 E911 configuration N0008589 3 3...
Page 380: ...380 Renumbering DNs N0008589 3 3...
Page 398: ...398 Saving wizard pages on your computer N0008589 3 3...
Page 458: ...458 Voice Mail settings N0008589 3 3...
Page 488: ...488 Setting system telco features N0008589 3 3...
Page 508: ...508 Other programming that affects public networking N0008589 3 3...
Page 522: ...522 PRI networking using Call by Call services N0008589 3 3...
Page 592: ...592 Monitoring Hunt groups N0008589 3 3...
Page 636: ...636 Configuring Double Density N0008589 3 3...
Page 640: ...640 Using the Network Update Wizard N0008589 3 3...
Page 666: ...666 Importing and Exporting DHCP data N0008589 3 3...
Page 722: ...722 Restarting the router N0008589 3 3...
Page 726: ...726 Important Web Cache considerations N0008589 3 3...
Page 748: ...748 Configuring an Interface with NAT N0008589 3 3...
Page 794: ...794 IPSec N0008589 3 3...
Page 818: ...818 Configuring the Policy Agent characteristics N0008589 3 3...
Page 832: ...832 Firewall rules for Business Communications Manager with Dialup interfaces N0008589 3 3...
Page 876: ...876 ISDN Programming N0008589 3 3...
Page 1004: ...1004 Index N0008589 3 3...