530
Creating tandem private networks
N0008589 3.3
Routing for tandem networks
In tandem networks each node needs to know how to route calls that do not terminate locally. To
do this, you set up routes for each connecting node by defining destination codes for each route.
If the node is also connected to the public network, the usual routing is required for that
connection.
The following tables show the routing tables for Node A and Node C for external and internal
terminating calls.
Note:
The PRI lines are enbloc dialing lines, so all dialed digits are collected before being dialed
out.
Node B
Node F
User on B dials a private DN for node F.
DN type: Private
Node B identifies it as being for node A and uses private trunk to route the call to A.
Incoming interface: Intercom
Destination: Remote node
Node A receives it and identifies it as being for C. Uses IP trunk to route call to C.
Incoming interface: Intercom
Destination: Remote node
Node C receives it and identifies it as being for D. Uses the private trunk to route call to
D.
Incoming interface: Intercom
Destination: Remote node
Node D receives it and identifies it as being for F. Uses the private trunk to route call to
F.
Incoming interface: Intercom
Destination: Remote node
Node F receives the call and identifies it as terminating locally. Uses target line to route
call. (Private received #)
Incoming interface: Private
Destination: Local (target line)
Table 117
Node A destination code table, external termination
Route
Absorb length
Destination code (public DNs)
4 (PSTN)
1
91604
3 (Node B)
0
91403762 (Node B)
3 (Node B)
0
91403765 (Node E)
4 (PSTN)
1
9140376* (not internal network)
4 (PSTN)
1
914037* (not internal network)
4 (PSTN)
1
91403* (not internal network)
4 (PSTN)
1
9* (not internal network)
* This wild card represents a single digit.
Table 116
Calls originating from the private network within a tandem network (Continued)
Received
Destination
Description
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...