Using routing to create networking
515
Programming Operations Guide
If a user in New York wants to call Toronto within the network, they dial 6221. The local Business
Communications Manager checks the number against the routing tables and routes the call
according to the destination code 6, which places the call using Route 001.
The call appears on the auto answer line on the Business Communications Manager in Santa Clara
as 6-221. Because 6 is programmed as a destination code for Toronto on the Santa Clara system,
another call is placed using route 002 from Santa Clara to Toronto. At the Toronto system, the
digits 6-221 are interpreted as a target line Private received number. The call now alerts at
telephone 6221 in Toronto.
Note:
Network calls that use routes are subject to any restriction filters in effect.
If the telephone used to make a network call has an appearance of a line used by the route, the call
will move from the intercom button to the Line button.
The telephone used to make a network call must have access to the line pool used by the route.
Network calls are external calls, even though they are dialed as if they were internal calls. Only the
features and capabilities available to external calls can be used.
When programming a button to dial a Network number automatically (autodial), network calls
must be treated as external numbers, even though they resemble internal telephone numbers.
Routes generally define the path between your Business Communications Manager switch and
another switch in your network, not other individual telephones on that switch.
Toronto office:
Parameter
Setting
Trunk/Line Data (external)
Line 093
T1 E&M
Answer Mode
Auto
Line type
Pool N
Target line (internal)
Line 300
Target line
Private Received #
6221
Line Access
DN 6221
L300: Ring only
Line pool access
Line pool N
Routing Destinations
Office #1
Office #2
Routing to
New York
Santa Clara
Route
001
Use
Pool N
External #
None
Destination Code
4
2
Absorb
None
None
Normal route
001
001
Table 112
E and M routing for a Business Communications Manager network (Continued)
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...